Re: ILE COBOL Data Exception on the 400

[Jon.Paris@xxxxxx]

 >> We have scoured the COBOL book, looking for an override option for this
handling ... no joy.

I don't think there is one - but it seems to me that the problem could be
fixed relatively simply during the process of converting the data to the
400.  If the MF code behaves as you say, then a simple program that
reads/writes with a MOVE corresponding would fix all the "spacey" numerics
for you.

Are you externally describing your files on the 400 (the recommended
approach) - if so then there are utilities that will run against the file
description and fix the data for you.  Can't recall any names right now but
I think one was published by News/400 some time back.  Of course if you
have done nothing to correct the programs that wrote the spaces in there in
the first place then the problem will just repeat ad-nauseum!!

No wishing to be nasty, but did you not have any consulting advice on the
conversion to warn you that these kinds of problems would occur?


+---
| This is the COBOL/400 Mailing List!
| To submit a new message, send your mail to COBOL400-L@midrange.com.
| To subscribe to this list send email to COBOL400-L-SUB@midrange.com.
| To unsubscribe from this list send email to COBOL400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---END