|
View previous topic :: View next topic
|
| Author |
Message |
Ayush Shrivastava
New User
Joined: 07 May 2020
Posts: 5
Location: India
|
|
|
|
Hi All,
I am trying to send an e-mail via JCL using IEBGENER utility. These below two characters are getting changed in the body of the mail.
'{' gets changed to 'æ'
'}' gets changed to 'å'
Somehow either outlook is not able to read them or there is some formatting issue. Maybe JCL is sending in plain text format whereas outlook is expecting html. Please suggest a solution. I tried using ASCII and html code of '{' in jcl as well but it didn't worked.
| Code: |
//AYUSH123 JOB (U811),'AYUSH',
// MSGCLASS=0,MSGLEVEL=(1,1),CLASS=U
//* EMAIL REPORT TO THE DESTINATION EMAIL ADDRESS
//EMAIL1 EXEC PGM=IEBGENER
//SYSUT1 DD *
TO=User1@xyz.com
SUBJECT=EVENT IN JSON
MSG=
{
A
B
C
D
}
//SYSUT2 DD SUBSYS=(ESF,A,,EMAIL123)
//SYSIN DD DUMMY
//SYSPRINT DD SYSOUT=*
|
Result:
æ
A
B
C
D
å |
|
| Back to top |
|
 |
prino
Senior Member
Joined: 07 Feb 2009
Posts: 1315
Location: Vilnius, Lithuania
|
|
|
|
| This is like telling the world your nose bleeds when you write JCL. |
|
| Back to top |
|
|
Joerg.Findeisen
Senior Member
Joined: 15 Aug 2015
Posts: 1335
Location: Bamberg, Germany
|
|
|
|
| Use the right Codepage for CA Spool Input or ask the guys in your shop how to do it properly. |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8700
Location: Dubuque, Iowa, USA
|
|
|
|
| Quote: |
| Somehow either outlook is not able to read them or there is some formatting issue |
Or the third possibility -- which is the actuality -- is that EBCDIC does not have braces in its standard character set and hence there is no standard defined conversion to ASCII for those characters. Square brackets and braces are some of the characters defined in ASCII that are not defined in EBCDIC, and hence they usually cause problems. If you want to know how to handle them, you need to talk to your site support group or the vendor for assistance. |
|
| Back to top |
|
|
Ayush Shrivastava
New User
Joined: 07 May 2020
Posts: 5
Location: India
|
|
|
|
Thanks all for the support. Correct codepage was not present in the LPAR where I was testing, however it worked in higher LPARs due to presence of correct codepage for conversion. Thanks again!  |
|
| Back to top |
|
|
|
|
