Your SAS® session might terminate abnormally if the text string that is submitted with the DOSUBL function contains PROC IMPORT or PROC EXPORT code. The problem also occurs when you invoke a macro that contains PROC IMPORT or PROC EXPORT code from within the DOSUBL function.
The example code below illustrates the problem:
The following circumvention uses CALL EXECUTE instead of the DOSUBL function that was shown in the DATA _NULL_ step above: