Re: Help!--ASCII vs MVS / Unpacked Signed Fields

In article <434h59$msg@mother.usf.edu> smorrow@dotrisc.cfr.usf.edu "Steve Morrow" writes: > You'll never believe the problem I've encountered now. Try us! :-) [SNIP] > In the "grand scheme" of the EBCIDIC world, a zero translates > to the ASCII char of 208, AKA hex D0. Thus, for a negative charge > of -$954.00, I would supply 0009540X (where X simply represents the > 'unprintable?' char of ASCII 208 in this case). > > Alas, I thought I could use the ASCII function to assign this char > to a variable and print it (for which it does in the report). However, > after batch processing on MVS, I'm getting $954.07 instead of > $954.00...where did the 7 cents come from????? Ummm, <scratch, scratch>, are you doing an ASCII to EBCDIC conversion when you do the FTP? If so, it may be doing something unprintable (excuse the pun!) to ASCII 208. HTH, Spokey the Wheeler------------------------------------------------------------- "Billy Boy" - das aufregend andere kondom!