Re: SENDFILE with SMTP
Hello Richard Schuh, Did you use the SMTP or MIME option in the SENDFILE? Ed Martin Aultman Health Foundation 330-363-5050 ext 35050 From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard Sent: Wednesday, September 30, 2009 7:16 PM To: IBMVM@LISTSERV.UARK.EDU Subject: SENDFILE with SMTP I am trying to send a report to e-mail addresses on a Windows based LAN using SENDFILE. Originally, the RECFM of the file was V. When the report arrived, the 5th line was concatenated to the 4th and the 10th to the 9th. All other lines were correct. There are no weird bytes at either end of any of the records. For the record, the current LRECL is 94, lines 4 and 5 are each 49 bytes, 9 is 50 and 10 is 32. There are other consecutive records having lengths that match either the 4-5 or the 9-10 combinations. This does not appear to be a record length problem I have tried various things while attempting to fix this: 1. x'15' at the end of every line. No concatenation, but every line was double-spaced. 2. x'15' at the end of lines 4 and 9. No concatenation, but 5 and 10 were double-spaced. 3. x'0D' at the end of each line. No affect, the error still occurred the same as the original failure. 4. x'0A' at the end of each line. Error still occurred, and there was a small square at the end of each line. 5. x'0D0A' at the end of each line. Double-spaced, concatenation still present, square as above. 6. Copied the file making the RECFM F, LRECL 94. Success. Other LRECLs 94 also work. Just for grins, I tried using HTML enrichment. The result was chaos, even if I sandwiched the report between pre and /pre tags. Now for the questions: Why just those two concatenations? Should any of those attempts have succeeded while the RECFM was V? I am perfectly willing to create the report as RECFM F. That will, however, require that I either make the LRECL something at least as large as the largest possible record (which is unknown at this time) or create the file as format V and then use 'COPYFILE fn ft fm (RECFM F' To convert it before sending the mail. The latter is the method that will cause the least pain. Regards, Richard Schuh
Re: SENDFILE with SMTP
I meant to respond to some of your other points... On Wednesday, 09/30/2009 at 07:17 EDT, Schuh, Richard rsc...@visa.com wrote: I have tried various things while attempting to fix this: 1. x'15' at the end of every line. No concatenation, but every line was double-spaced. 2. x'15' at the end of lines 4 and 9. No concatenation, but 5 and 10 were double-spaced. EBCDIC NL is translated to ASCII LF by the STANDARD translation table. 3. x'0D' at the end of each line. No affect, the error still occurred the same as the original failure. Not translated. 0x0D is CR in both dialects. A standalone CR has no visual effect. 4. x'0A' at the end of each line. Error still occurred, and there was a small square at the end of each line. EBCDIC control character RPT is translated to ASCII 0x1A. If a DOS program were to process the file, it would be logical EOF. EBCDIC LF is 0x25, which is translated by STANDARD to ASCII LF (0x0A). 5. x'0D0A' at the end of each line. Double-spaced, concatenation still present, square as above. See above. 6. Copied the file making the RECFM F, LRECL 94. Success. Other LRECLs 94 also work. Just for grins, I tried using HTML enrichment. The result was chaos, even if I sandwiched the report between pre and /pre tags. Now for the questions: Why just those two concatenations? Should any of those attempts have succeeded while the RECFM was V? Yes. Well, maybe. The question is: What is in the file? A hex editor on your PC will tell you. My question about What form of SENDFILE did you use? goes to the heart of the issue. 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. Alan Altmark z/VM Development IBM Endicott
Re: SENDFILE with SMTP
SMTP. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Edward M Martin Sent: Thursday, October 01, 2009 6:42 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SENDFILE with SMTP Hello Richard Schuh, Did you use the SMTP or MIME option in the SENDFILE? Ed Martin Aultman Health Foundation 330-363-5050 ext 35050 From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard Sent: Wednesday, September 30, 2009 7:16 PM To: IBMVM@LISTSERV.UARK.EDU Subject: SENDFILE with SMTP I am trying to send a report to e-mail addresses on a Windows based LAN using SENDFILE. Originally, the RECFM of the file was V. When the report arrived, the 5th line was concatenated to the 4th and the 10th to the 9th. All other lines were correct. There are no weird bytes at either end of any of the records. For the record, the current LRECL is 94, lines 4 and 5 are each 49 bytes, 9 is 50 and 10 is 32. There are other consecutive records having lengths that match either the 4-5 or the 9-10 combinations. This does not appear to be a record length problem I have tried various things while attempting to fix this: 1. x'15' at the end of every line. No concatenation, but every line was double-spaced. 2. x'15' at the end of lines 4 and 9. No concatenation, but 5 and 10 were double-spaced. 3. x'0D' at the end of each line. No affect, the error still occurred the same as the original failure. 4. x'0A' at the end of each line. Error still occurred, and there was a small square at the end of each line. 5. x'0D0A' at the end of each line. Double-spaced, concatenation still present, square as above. 6. Copied the file making the RECFM F, LRECL 94. Success. Other LRECLs 94 also work. Just for grins, I tried using HTML enrichment. The result was chaos, even if I sandwiched the report between pre and /pre tags. Now for the questions: Why just those two concatenations? Should any of those attempts have succeeded while the RECFM was V? I am perfectly willing to create the report as RECFM F. That will, however, require that I either make the LRECL something at least as large as the largest possible record (which is unknown at this time) or create the file as format V and then use 'COPYFILE fn ft fm (RECFM F' To convert it before sending the mail. The latter is the method that will cause the least pain. Regards, Richard Schuh
Re: SENDFILE with SMTP
I tried MIME and, unfortunately, the results were the same. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Edward M Martin Sent: Thursday, October 01, 2009 6:42 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SENDFILE with SMTP Hello Richard Schuh, Did you use the SMTP or MIME option in the SENDFILE? Ed Martin Aultman Health Foundation 330-363-5050 ext 35050 From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard Sent: Wednesday, September 30, 2009 7:16 PM To: IBMVM@LISTSERV.UARK.EDU Subject: SENDFILE with SMTP I am trying to send a report to e-mail addresses on a Windows based LAN using SENDFILE. Originally, the RECFM of the file was V. When the report arrived, the 5th line was concatenated to the 4th and the 10th to the 9th. All other lines were correct. There are no weird bytes at either end of any of the records. For the record, the current LRECL is 94, lines 4 and 5 are each 49 bytes, 9 is 50 and 10 is 32. There are other consecutive records having lengths that match either the 4-5 or the 9-10 combinations. This does not appear to be a record length problem I have tried various things while attempting to fix this: 1. x'15' at the end of every line. No concatenation, but every line was double-spaced. 2. x'15' at the end of lines 4 and 9. No concatenation, but 5 and 10 were double-spaced. 3. x'0D' at the end of each line. No affect, the error still occurred the same as the original failure. 4. x'0A' at the end of each line. Error still occurred, and there was a small square at the end of each line. 5. x'0D0A' at the end of each line. Double-spaced, concatenation still present, square as above. 6. Copied the file making the RECFM F, LRECL 94. Success. Other LRECLs 94 also work. Just for grins, I tried using HTML enrichment. The result was chaos, even if I sandwiched the report between pre and /pre tags. Now for the questions: Why just those two concatenations? Should any of those attempts have succeeded while the RECFM was V? I am perfectly willing to create the report as RECFM F. That will, however, require that I either make the LRECL something at least as large as the largest possible record (which is unknown at this time) or create the file as format V and then use 'COPYFILE fn ft fm (RECFM F' To convert it before sending the mail. The latter is the method that will cause the least pain. Regards, Richard Schuh
Re: SENDFILE with SMTP
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. 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
Re: SENDFILE with SMTP
On Thu, 1 Oct 2009 10:39:02 -0700, Schuh, Richard rsc...@visa.com wrote : Is there a hex editor that is included with Office 2003 or with WinXP? W e 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. Perhaps uploading it as a binary file to CMS and displaying it in hex wit h either REXX or a PIPE would meet your needs. Brian Nielsen
Re: SENDFILE with SMTP
On Thu, 1 Oct 2009 13:55:22 -0500, Brian Nielsen bniel...@sco.idaho.gov wrote: On Thu, 1 Oct 2009 10:39:02 -0700, Schuh, Richard rsc...@visa.com wrot e: 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. Perhaps uploading it as a binary file to CMS and displaying it in hex with either REXX or a PIPE would meet your needs. ...or even XEDIT. Brian Nielsen
Re: SENDFILE with SMTP
There is a free hex editor by cyngus. You can get it here: http://www.softcircuits.com/cygnus/fe/ Frank M. Ramaekers Jr. Systems Programmer MCP, MCP+I, MCSE RHCE American Income Life Insurance Co. Phone: (254)761-6649 1200 Wooded Acres Dr.Fax: (254)741-5777 Waco, Texas 76710 -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard Sent: Thursday, October 01, 2009 12:39 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SENDFILE with SMTP 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. 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 _ This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this in error, please destroy it immediately and notify us at privacy...@ailife.com.
Re: SENDFILE with SMTP
The price is too high. 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. Regards, Richard Schuh There is a free hex editor by cyngus. You can get it here: http://www.softcircuits.com/cygnus/fe/ Frank M. Ramaekers Jr. Systems Programmer MCP, MCP+I, MCSE RHCE American Income Life Insurance Co. Phone: (254)761-6649 1200 Wooded Acres Dr.Fax: (254)741-5777 Waco, Texas 76710
Re: SENDFILE with SMTP
Frank, Re-read his line: 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. That's one of the challenges of working for large companies: lots of bureaucracy that requires many layers of management approval for the installation of anything new. But there is a good business case for that paranoia -- protecting the very resources that got them to become a large company in the first place. Mike Walter Hewitt Associates The opinions expressed herein are mine alone, not my employer's. Frank M. Ramaekers framaek...@ailife.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 10/01/2009 02:13 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: SENDFILE with SMTP There is a free hex editor by cyngus. You can get it here: http://www.softcircuits.com/cygnus/fe/ Frank M. Ramaekers Jr. Systems Programmer MCP, MCP+I, MCSE RHCE American Income Life Insurance Co. Phone: (254)761-6649 1200 Wooded Acres Dr.Fax: (254)741-5777 Waco, Texas 76710 -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard Sent: Thursday, October 01, 2009 12:39 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SENDFILE with SMTP 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. 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 _ This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this in error, please destroy it immediately and notify us at privacy...@ailife.com. The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
Re: SENDFILE with SMTP
The business case is especially strong considering our business. Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mike Walter Sent: Thursday, October 01, 2009 12:35 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SENDFILE with SMTP Frank, Re-read his line: 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. That's one of the challenges of working for large companies: lots of bureaucracy that requires many layers of management approval for the installation of anything new. But there is a good business case for that paranoia -- protecting the very resources that got them to become a large company in the first place. Mike Walter Hewitt Associates The opinions expressed herein are mine alone, not my employer's. Frank M. Ramaekers framaek...@ailife.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 10/01/2009 02:13 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: SENDFILE with SMTP There is a free hex editor by cyngus. You can get it here: http://www.softcircuits.com/cygnus/fe/ Frank M. Ramaekers Jr. Systems Programmer MCP, MCP+I, MCSE RHCE American Income Life Insurance Co. Phone: (254)761-6649 1200 Wooded Acres Dr.Fax: (254)741-5777 Waco, Texas 76710 -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard Sent: Thursday, October 01, 2009 12:39 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SENDFILE with SMTP 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. 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 _ This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this in error, please destroy it immediately and notify us at privacy...@ailife.com. The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
Re: SENDFILE with SMTP
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
Re: SENDFILE with SMTP
There isn't, but if all you want to do is display the HEX I can send you a WORD file with a macro to read and display it. Is that allowed or is VBSCRIPT disabled/not permitted... Dave G4UGM -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Brian Nielsen Sent: 01 October 2009 19:55 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SENDFILE with SMTP On Thu, 1 Oct 2009 10:39:02 -0700, Schuh, Richard rsc...@visa.com wrote : Is there a hex editor that is included with Office 2003 or with WinXP? W e 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. Perhaps uploading it as a binary file to CMS and displaying it in hex wit h either REXX or a PIPE would meet your needs. Brian Nielsen
