Re: Another QtmmSendMail problem?

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.