On Thu, Oct 1, 2009 at 1:39 PM, Schuh, Richard <rsc...@visa.com> wrote:
> > Yes. Well, maybe. The question is: What is in the file? A > > hex editor on your PC will tell you. > > The source file, if I haven't copied it adding strange bytes while trying > to find the secret, is strictly printable EBCDIC, comprised of the > characters a-z (upper and lower case) digits 0-9, blanks, and the characters > "-/." (at least there were no others in my test file). > > Is there a hex editor that is included with Office 2003 or with WinXP? We > have zero-tolerance prohibitions against installing unapproved software, and > most everything falls into that category. There are none that I can find in > the approved list. > > debug.exe is in WinXP. Pretty crude, but it should do the job for this case. You can find some instructions at: http://mirror.href.com/thestarman/asm/debug/debug.htm > > My question about "What > > form of SENDFILE did you use?" goes to the heart of the > > issue. > > Both SMTP and, as of this morning, MIME. > > > Files sent in the plain-text body of the e-mail will > > be subjected to any and all re-encoding required to get it > > past the SMTP "sensor net" looking for SMTP controls. CRLFs > > are the usual victims. By using the MIME options on > > SENDFILE, the file will be encoded in a way that insulates > > the file from such predations. > > Looks like I will have to either convert to RECFM F or send it as an > attachment. > > Late breaking news - appending x'05' to each record works regardless of > whether SMTP or MIME is specified. > > > > > Alan Altmark > > z/VM Development > > IBM Endicott > >
