A DM statement or combination of DM and ODS statements that follow an ABORT CANCEL statement might cause your SAS^® session to stop responding. The ABORT CANCEL statement should cause the execution of the submitted statements to be canceled. The code below replicates the issue and causes your SAS session to stop responding:

data _null_;
   put 'NOTE: Cancel was used to prevent a submit all.';
   abort cancel nolist;
run;

data work.class;
   set sashelp.class;
run;

dm 'output';

If you attempt to break out of the SAS session, a dialog box stating that SAS is busy appears with the following options:

• Terminate the SAS System
• Interrupt the current process
• Do nothing

Interrupting the current process frees the cursor. However, subsequent SAS statements are not processed because the SAS session is caught in an infinite loop. The title bar displays "Processing submitted statements".

To terminate your SAS session, you must select the "Terminate the SAS System" option twice, and answer "No" to the question "Do you wish to wait for SAS to terminate normally?"

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for this issue for Base SAS 9.4_M3 is available at: