Problem Note 66233: The SAS® session fails with a segmentation violation when you use a long value in the FROM= option in a FILENAME EMAIL statement
 |  |  |  |  |
If you use a FILENAME EMAIL statement with a long value in the FROM= option, the SAS session might fail with a traceback similar to the following:
/SASHome/SASFoundation/9.4/sasexe/sas(+0x16840e) [0x56548256a40e]
/SASHome/SASFoundation/9.4/sasexe/sas(+0x4eddf) [0x565482450ddf]
/SASHome/SASFoundation/9.4/sasexe/tkmk.so(bkt_signal_handler+0x144)
[0x7f3402190ac4]
/lib64/libpthread.so.0(+0x12d80) [0x7f3403624d80]
/SASHome/SASFoundation/9.4/sasexe/tkmk.so(skmMemRelease+0x190)
[0x7f34021a2cd0]
/SASHome/SASFoundation/9.4/dbcs/sasexe/sasvmail(vxesmtp+0x1244)
[0x7f33ddb52964]
/SASHome/SASFoundation/9.4/dbcs/sasexe/sasvmail(vxesend+0x28)
[0x7f33ddb4d418]
/SASHome/SASFoundation/9.4/dbcs/sasexe/sasvmail(yxeclose+0x185)
[0x7f33ddb4b055]
/SASHome/SASFoundation/9.4/dbcs/sasexe/sasxkern(yxclose+0x1f)
[0x7f33ed4a883f]
/SASHome/SASFoundation/9.4/sasexe/sasdsa(dsafcls+0x9e) [0x7f33dd2d96fe]
/SASHome/SASFoundation/9.4/dbcs/sasexe/sasdsx(dseclos+0x2b2)
[0x7f33dc31f7e2]
/SASHome/SASFoundation/9.4/dbcs/sasexe/sasdsx(dsxxtrm+0xd2)
[0x7f33dc30d452]
/SASHome/SASFoundation/9.4/sasexe/sasds(dsexec+0x75) [0x7f33dd911165]
/SASHome/SASFoundation/9.4/sasexe/sasds(sasds+0x4ae2) [0x7f33dd90a7d2]
/SASHome/SASFoundation/9.4/sasexe/sas(vvtentr+0x18a) [0x56548245093a]
/lib64/libpthread.so.0(+0x82de) [0x7f340361a2de]
/lib64/libc.so.6(clone+0x43) [0x7f3402b9ba63]
/SASHome/SASFoundation/9.4/sasexe/sas(+0x4eddf) [0x565482450ddf]
/SASHome/SASFoundation/9.4/sasexe/tkmk.so(bkt_signal_handler+0x144)
[0x7f3402190ac4]
/lib64/libpthread.so.0(+0x12d80) [0x7f3403624d80]
/SASHome/SASFoundation/9.4/sasexe/tkmk.so(skmMemRelease+0x190)
[0x7f34021a2cd0]
/SASHome/SASFoundation/9.4/dbcs/sasexe/sasvmail(vxesmtp+0x1244)
[0x7f33ddb52964]
/SASHome/SASFoundation/9.4/dbcs/sasexe/sasvmail(vxesend+0x28)
[0x7f33ddb4d418]
/SASHome/SASFoundation/9.4/dbcs/sasexe/sasvmail(yxeclose+0x185)
[0x7f33ddb4b055]
/SASHome/SASFoundation/9.4/dbcs/sasexe/sasxkern(yxclose+0x1f)
[0x7f33ed4a883f]
/SASHome/SASFoundation/9.4/sasexe/sasdsa(dsafcls+0x9e) [0x7f33dd2d96fe]
/SASHome/SASFoundation/9.4/dbcs/sasexe/sasdsx(dseclos+0x2b2)
[0x7f33dc31f7e2]
/SASHome/SASFoundation/9.4/dbcs/sasexe/sasdsx(dsxxtrm+0xd2)
[0x7f33dc30d452]
/SASHome/SASFoundation/9.4/sasexe/sasds(dsexec+0x75) [0x7f33dd911165]
/SASHome/SASFoundation/9.4/sasexe/sasds(sasds+0x4ae2) [0x7f33dd90a7d2]
/SASHome/SASFoundation/9.4/sasexe/sas(vvtentr+0x18a) [0x56548245093a]
/lib64/libpthread.so.0(+0x82de) [0x7f340361a2de]
/lib64/libc.so.6(clone+0x43) [0x7f3402b9ba63]
NOTE: The SAS System stopped processing this step because of errors.
ERROR: An exception has been encountered.
Please contact technical support and provide them with the following traceback
information:
The SAS task name is [DATASTEP]
Segmentation Violation
ERROR: An exception has been encountered.
Please contact technical support and provide them with the following traceback
information:
The SAS task name is [DATASTEP]
Segmentation Violation
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | Base SAS | z/OS | 9.4_M6 | 9.4 TS1M6 | ||
| z/OS 64-bit | 9.4_M6 | 9.4 TS1M6 | ||||
| Microsoft® Windows® for x64 | 9.4_M6 | 9.4 TS1M6 | ||||
| 64-bit Enabled AIX | 9.4_M6 | 9.4 TS1M6 | ||||
| 64-bit Enabled Solaris | 9.4_M6 | 9.4 TS1M6 | ||||
| HP-UX IPF | 9.4_M6 | 9.4 TS1M6 | ||||
| Linux for x64 | 9.4_M6 | 9.4 TS1M6 | ||||
| Solaris for x64 | 9.4_M6 | 9.4 TS1M6 | ||||
A fix for this issue for Base SAS 9.4_M6 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/D9T.html#66233| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2020-07-13 08:39:25 |
| Date Created: | 2020-07-01 09:21:30 |