|
I'm not sure if you're asking for ideas on how SMTP might be mis-configured; if you're looking for ideas on how to process the files given that they have the wrong code page attribute; or how this might be related to the subject of creating a *STMF; but: For your configuration, who is the recipient (OV/400, POP, etc.) of the SMTP note? Where/when are you accessing these files? How are you determining that the file contents really are 819? For how to possibly get around the current attribute: If you are on V4R4 you could use the Integrated File System Qp0lSetAttr() API to change the code page from 37 to 819 and then open the IFS file. Alternatively, on earlier releases, you could change your application to open the file in binary mode (no conversion to the job CCSID takes place then) and treat the data as 819 directly. Bruce > >On this note, I am trying to read IFS files that the IBM SMTP server has >designated as code page 37, however it is actually codepage 819. These are >incoming E-Mails. The API's obviously don't read the data correctly since >they think the code page is 37. > >I am doing a large number of I/O and am currently using the CL commands to >copy the data for reading, however this is very time and processor >consuming. I have called IBM support and opened up a call, however they >cannot figure out a resolution to this problem. > >Any ideas? > +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.