Hi:   This Tech Support note implies that you might need to use the SENDER option and make FROM and SENDER the same: http://support.sas.com/kb/11/592.html and then this Tech Support note has some more explanation. http://support.sas.com/kb/5/000.html Here's the paragraph from the second note:   "Since MVS does not have the EMAILID system option, the FILENAME option "SENDER" or the !EM directive, "!EM_SENDER!" can be used to specify the desired e-mail address of the sender.  The sender should not be confused with the FROM e-mail address.  The option and directive are available for all hosts."   If you need more help, then you might want to open a track with Tech Support. cynthia ... View more

Oh. The reason the ELSE loop is satisfied in your code is that you have used the comparison if &SYSJOBID EQ "AC11895K" The macro variable &SYSJOBID does not contain a quoted value; your job ID really is AC11895K, right? So then the comparison fails because AC11895K does not equal "AC11895K"! The comparison will work with either of the following (and maybe other forms, too): %if &SYSJOBID =  AC11895K (in macro code)      or if "&SysJobId" = "AC11895K" (in data step code) I hope this helps. ... View more

As you said SAS is not the issue. While it is being written to excel, the format through tagattr does not reflect in excel columns,however dynamically, the data gets formatted (character '075E00' gets formatted as 000075) We are trying to attach a mianframe dataset information in .XLS format and sending a mail to some third party users. We are achcieving this conversion of PS file to XLS file through SAS utility by using ODS tagsets excelxp statements via XML fomratting. While writing the XML code(to generate xls), the alphanumeric data with value 'E' inbetween numbers are treated as numeric and truncation happens. For example if the data is 075E00 in mainframe file, the excel is displaying it as 000075(i.e 75 * 10^0 = 75) which is scientific representation of numbers. We need to report the real data and we dont need such truncation to happen. Tried with lots of formatting overrides available with ODS tagsets commands but nothing worked. Based on the value, the alphanumeric column is interpreting its own data type in the XML code. Code chunk: PROC PRINT DATA=INREPT1 noobs;   VAR GROUP/ style={tagattr='type:String/text format:####'  htmlstyle="mso-number-format:'\@'"}; Even with this specification, the numeric type override happens for this particular input. Kindly suggest any other approach to overcome this. Thanks! ... View more