In reply to Chris Hemedinger.

Hi Chris, thanks for replying. No, I didn't change Async - was not even aware of that property. Just as an experiment, I went back to the original example code, and added 2 more simple steps to the proc means: proc sort and proc print. I observe the same effect as before. Below I've pasted what is written to the console. Note the source statements for all 3 steps appear as one continuous block of text; then that is followed by the messages for each step, absent the source statements.

Is it possible that different defaults might somehow be set on the server side? I'd be really curious what result you are seeing with your log; I can't tell just from the screen shot above, as only the first line of the log is visible.

NOTE: The autoexec file, E:\SAS\Config\Lev1\SASApp\WorkspaceServer\autoexec.sas, was executed at server initial
ization.
1 options formchar='|----|+|---+=|-/\*';ods listing; proc means data=sashelp.cars mean mode min max;
run;proc sort
1 ! data=sashelp.cars out=work.cars; by origin type; run;proc print data=work.cars; where make='Volv
o'; var make model msrp
1 ! invoice; run;

NOTE: There were 428 observations read from the data set SASHELP.CARS.
NOTE: The PROCEDURE MEANS printed page 1.
NOTE: PROCEDURE MEANS used (Total process time):
real time 0.01 seconds
cpu time 0.01 seconds

NOTE: There were 428 observations read from the data set SASHELP.CARS.
NOTE: The data set WORK.CARS has 428 observations and 15 variables.
NOTE: PROCEDURE SORT used (Total process time):
real time 0.00 seconds
cpu time 0.00 seconds

NOTE: There were 12 observations read from the data set WORK.CARS.
WHERE make='Volvo';
NOTE: The PROCEDURE PRINT printed page 2.
NOTE: PROCEDURE PRINT used (Total process time):
real time 0.00 seconds
cpu time 0.00 seconds