Re: Strange issue maybe you can help me with Mark

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.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: "RPGLIST" <rpglist@xxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>,

Date: 04/10/2013 10:22 AM
Subject: Strange issue maybe you can help me with Mark
Sent by: midrange-l-bounces@xxxxxxxxxxxx



I've got a normal file (DDS created) that I added a new field to, and then
recompiled. Everything fine so far.

I have a program that is writing data to this file but is not writing
anything to the new field, the write occurs without hiccup. I should
mention the write is being done like the following:

Write FileName MyDataDs;

The data structure is defined as an output file *Output.

I have a second program that is reading this file and its reading it into
a data structure, but its 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.


--
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.