× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



It could be uninitialized variable.
It frequently happens that initial value for unitialized variable is
different when program is under debug.

    Alexei Pytel
speaking only for myself




                      "Andrew Goade"
                      <agoade@hubgroup.        To:       rpg400-l@midrange.com
                      com>                     cc:
                      Sent by:                 Subject:  RE: RPG ILE Write
                      rpg400-l-admin@mi
                      drange.com


                      03/18/2002 12:44
                      PM
                      Please respond to
                      rpg400-l






The job log does not display anything.  It seems like the program thinks it
worked.  The program does not abend, so it isn't a duplicate key issue.
Some of records do get written, so it's not a library list issue.  We don't
use commitment control, so that is out of the question.  And the program
logic isn't wrong because the record writes when we step through it in
Debug.  It might be a RPG issue, where would I look for that type of
information??




                    Jim Langston
                    <jlangston@celsin       To:
"'rpg400-l@midrange.com'" <rpg400-l@midrange.com>
                    c.com>                  cc:
                    Sent by:                Subject:     RE: RPG ILE Write
                    rpg400-l-admin@mi
                    drange.com


                    03/18/2002 12:31
                    PM
                    Please respond to
                    rpg400-l






What does your job log show you, anything?  DSPJOBLOG and hit F10 to
display
all and scroll down.

The first thing I could think that would cause a record not to be written
would be duplicate keys.  Second would be library list issues.  Third would
be commitment control.  Fourth would be program logic.  Fifth would be bug
in RPG.

Regards,

Jim Langston

-----Original Message-----
From: Andrew Goade [mailto:agoade@hubgroup.com]

For the records it doesn't write normally, it writes them in Debug.
Basically, I have a record, let's say it's record 123.  I make a table
change to 123, and it flows through my process.  However, my record doesn't
write to my file.  Now, I put my process in debug.  Again I make a change
to 123.  When I break at the write and F10 through it, the record now
appears in my file.  Now let's say that I enddbg and make a change to
record 456.  It flows through my process and writes to my file.  This is
not dependant on debug.  It will happen this way before or after I
start/stop debug.
_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
or email: RPG400-L-request@midrange.com
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@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
or email: RPG400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.







As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

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