AS400 – SNDDST comand with attachments.
Hi, I am using the SNDDST command to send attachments to my own email address on MS Outlook 2003. The following are the commands i use:
[strong]CPYTOPCD FROMFILE(MYLIB/MYFILE) TOFLR(TEMP) TODOC(MYFILE.TXT) REPLACE(*YES)[/strong]
[strong] [/strong]
[strong]SNDDST TYPE(*DOC) TOINTNET((my.name@company.com)) DSTD(A) MSG(Message) DOC(FILE.TXT) FLR(TEMP)[/strong]
When open the attachement on the email that i recieve some of the text is unreadable. i.e. it seems to have a problem with spaces, decimal points and commas.
I get the same result with .XLS, .CSV, .RTF and .PDF wont open at all. In .xls and .csv it also does not format in the correct columns.
Can anyone suggest a way around these issues?
Many Thanks
Software/Hardware used:
AS400, SNDDST, OS/400 V5R4M5
[strong]CPYTOPCD FROMFILE(MYLIB/MYFILE) TOFLR(TEMP) TODOC(MYFILE.TXT) REPLACE(*YES)[/strong]
[strong] [/strong]
[strong]SNDDST TYPE(*DOC) TOINTNET((my.name@company.com)) DSTD(A) MSG(Message) DOC(FILE.TXT) FLR(TEMP)[/strong]
When open the attachement on the email that i recieve some of the text is unreadable. i.e. it seems to have a problem with spaces, decimal points and commas.
I get the same result with .XLS, .CSV, .RTF and .PDF wont open at all. In .xls and .csv it also does not format in the correct columns.
Can anyone suggest a way around these issues?
Many Thanks
Software/Hardware used:
AS400, SNDDST, OS/400 V5R4M5
ASKED:
March 19, 2010 3:42 PM
UPDATED:
March 19, 2010 6:32 PM
Answer Wiki:
Don't use CPYTOPCD. Use CPYTOIMPF instead. It allows you to specify an EBCDIC to PCASCII conversion during the copy.
To see all answers submitted to the Answer Wiki: View Answer History.
Run QRYDOCLIB FLR(TEMP) OUTFILE(QTEMP/MYDOCL).
After the document list is written to the outfile, use RUNQRY to see the Data Character Set and Code Page values. Post them here. Most likely, your CPYTOPCD isn’t using the appropriate translate table. (And seeing the CPYTOPCD command that you used would be helpful.)
However, I’d also say that CPYTOPCD isn’t appropriate — unless you’re still using Windows 95 or 98 at most. It can be made to work, but it can’t be guaranteed to keep working in the future.
Tom