I have a map definition where every field is set with the "modified data" flag on (not my choice). It also has EXTATT=YES, which may be causing the problem.
The problem is, if I change a field's map-out attribute (to highlight a field, for example) and then issue a SEND MAP DATAONLY command, then issue a RETURN with a TRANID, when the control comes back into the program, that particular field's map-in value is low-values and map-in length is 0.
If I do not change the field's attribute, upon return to the program, the field's map-in value is retained and map-in length is 4 (because of the modified data flag being on in the map definition).
Is anyone familiar with this and know why this is happening and how I might be able to set the attribute AND retain the map-in value and length on the return?
It never fails-- I spend 4 hours on a silly issue like this, finally post it in a forum as a last resort and then 10 minutes later find the solution.
I was assigning ALPHA-BRT to the attribute (x'C8'), and I was supposed to be using ALPHA-BRT-MDT (x'C9'). I guess x'C9' forces the modified data tag to remain on... or something.... bleh anyway it's working fine now, YAY!