Re: Strange issue maybe you can help me with Mark

If that understanding is correct, then using SQL DDL to create the
file being written-to would /fix/ the issue with the "second program
that is reading this file" and thus getting an error, and thus would
suffice to "avoid this issue" with the 2nd program getting an error ;-)

I am still wondering what a "0404" error is. Seems nobody has ever
mentioned "0404" on the RPG list... according to search results. The OP
said that "I added a new field", but no mention was made of the data
type of the field. Odd how often so little is offered-up about failing
scenarios people are having, when they come asking for help :-( And
such informative subject lines too; those going to the archives for help
on similar issues sure are hopeful they have found an appropriate
message thread when they read those titles!

I think Rob's second point was his primary impetus in replying, but I
may be wrong about that.

Regards, Chuck

On 10 Apr 2013 07:57, Anderson, Kurt wrote:

If I understand correctly, using DDL would have caused the program
to blow up on the write instead of writing junk. I'm not saying
that's bad, but I will say that doesn't fix the issue he's having.

rob@xxxxxxxxx on Wednesday, April 10, 2013 9:44 AM wrote:

My initial suggestion would be to stop using DDS to define files
and you'll stop getting X'4040' crap into numeric columns. DDL
defined files will stop that, unlike DDS defined files. Failing
that, then take your question to the RPG list for further
breakdown.

"RPGLIST" on 04/10/2013 10:22 AM wrote:

<<SNIP>> I have a second program that is reading this file and
it's reading it into a data structure, but it's throwing a 0404
error on the new field.

I found a workaround of INZ'ng the file when I write but is that
really necessary?

How do I avoid this issue?

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.