|
I've also tried changing my job CCSID to the one that isn't working on my machine, but things worked just fine. Is that not the same? If not, how could I set up my job to test? Thanks! On Tue, 21 Dec 2004 11:01:11 -0600 Bruce Vining <bvining@xxxxxxxxxx> wrote: > > > > > This would not be causing the problem you're currently > working on but I > would recommend using DFTCCSID rather than CCSID on your > RTVJOBA. > > CCSID can legitimately be 65535 which would disable > conversions to 500 > while DFTCCSID will always be a valid non-65535 CCSID > value. Basically if > CCSID is not 65535 then DFTCCSID is set to CCSID. If > CCSID is 65535 then > DFTCCSID is calculated based on the LANGID of the job and > a conversion to > 500 can be attempted. > > > > > > > "Brad Stone" > > <brad@xxxxxxxxxxx > > m> > To > > Sent by: Midrange Systems > Technical > midrange-l-bounce Discussion > > s@xxxxxxxxxxxx > <midrange-l@xxxxxxxxxxxx> > > cc > > > 12/21/2004 10:49 > Subject > AM Re: Another > QtmmSendMail problem? > > > > > Please respond to > > Midrange Systems > > Technical > > Discussion > > > > > > > > > > The source CCSID was retrieved using RTVJOBA and CCSID. > > It's odd.. a while back before IBM said to convert to > CCSID > 500 most non US code pages had problems. Then after this > came along it seemed to work. But now here is a > situation > that is causing a problem. > > I did change the conversion for them to use iConv instead > of the API, but with the time difference won't know if it > worked until tommorow. > > Thanks... any more ideas, I'm all ears. > > Brad > > On Tue, 21 Dec 2004 10:42:35 -0600 > Bruce Vining <bvining@xxxxxxxxxx> wrote: > > > > > > > > > > How are they performing the CCSID conversion to 500? > The > > @ is x'7C' in > > both 500 and 870 so my first suspicion is that someone > > has hardcoded the > > source CCSID for conversion as 273 which would cause > this > > problem if the > > input is really 870... > > > > > > > > > > > > > > > "Brad Stone" > > > > <brad@xxxxxxxxxxx > > > > m> > > > To > > > > Sent by: Midrange Systems > > Technical > > midrange-l-bounce Discussion > > > > s@xxxxxxxxxxxx > > <midrange-l@xxxxxxxxxxxx> > > > > > cc > > > > > > > 12/21/2004 08:51 > > Subject > > AM Another > > QtmmSendMail problem? > > > > > > > > > > > > Please respond to > > > > Midrange Systems > > > > Technical > > > > Discussion > > > > > > > > > > > > > > > > > > > > > > I have a user that is having issues with the > QtmmSendMail > > API and their CCSID. > > > > The application does convert the addresses to CCSID 500 > > before sending. > > > > They normally run jobs with CCSID of 273. Things work > > fine. > > > > But they have a few users who use a Job CCSID of 870. > > With > > these, it seems like the old problem of the @ getting > > converted to the § is back again. The API does error > out > > saying the address is invalid. > > > > But, if they use § instead of @, things work fine again > > for > > users with the CCSID of 870. > > > > Any ideas on what could be happening here? Any way I > > could > > test on my end? I tried changing to CCSID 870 for my > job > > but things worked just fine. > > > > Thanks! > > > > Brad > > -- > > This is the Midrange Systems Technical Discussion > > (MIDRANGE-L) mailing list > > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > > To subscribe, unsubscribe, or change list options, > > visit: > > http://lists.midrange.com/mailman/listinfo/midrange-l > > or email: MIDRANGE-L-request@xxxxxxxxxxxx > > Before posting, please take a moment to review the > > archives > > at http://archive.midrange.com/midrange-l. > > > > > > > > > > -- > > This is the Midrange Systems Technical Discussion > > (MIDRANGE-L) mailing list > > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > > To subscribe, unsubscribe, or change list options, > > visit: > > http://lists.midrange.com/mailman/listinfo/midrange-l > > or email: MIDRANGE-L-request@xxxxxxxxxxxx > > Before posting, please take a moment to review the > > archives > > at http://archive.midrange.com/midrange-l. > > > > Bradley V. Stone > BVS.Tools > www.bvstools.com > -- > This is the Midrange Systems Technical Discussion > (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: > http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the > archives > at http://archive.midrange.com/midrange-l. > > > > > -- > This is the Midrange Systems Technical Discussion > (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: > http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the > archives > at http://archive.midrange.com/midrange-l. > Bradley V. Stone BVS.Tools www.bvstools.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.