topic Output ‘PearsonCorr’ was not created in Statistical Procedures

Output ‘PearsonCorr’ was not created

jason4sas — Thu, 04 Jan 2024 19:51:44 GMT

I have this simple snippet in SAS9,

ods select PearsonCorr;
ods output PearsonCorr=RA_RF_PearsonCorr;
        proc corr data=RA_COST_&ra_condition._all rank pearson;
            var &response_cost.;
            with &ra_rf_st_flag_vars.;
        run;

NOTE: The data set WORK.RA_RF_PEARSONCORR has 12 observations and 4 variables.
NOTE: Compressing data set WORK.RA_RF_PEARSONCORR increased size by 100.00 percent.
Compressed is 2 pages; un-compressed would require 1 pages.
WARNING: Output ‘PearsonCorr’ was not created. Make sure that the output object name, label, or path is spelled correctly. Also, verify that the appropriate *
* procedure options are used to produce the requested output object. For example, verify that the NOPRINT option is not used.
NOTE: PROCEDURE CORR used (Total process time):
real time 0.01 seconds
user cpu time 0.01 seconds

I could not find anything wrong with it. Also, strangely the same snippet is running fine in SAS Viya4. How to block it from happening in SAS9?

Re: Output ‘PearsonCorr’ was not created

ballardw — Thu, 04 Jan 2024 20:12:47 GMT

Replace all of the macro variables with the actual text. Run the procedure, show us the entire log for running the procedure, the code and all the messages. I suggest removing the ODS SELECT to debug code.

The data set was created with the output. That is what writes this:

NOTE: The data set WORK.RA_RF_PEARSONCORR has 12 observations and 4 variables.

So I am a bit confused about the notes shown, which is why I request a complete run that we can read.

Re: Output ‘PearsonCorr’ was not created

PaigeMiller — Thu, 04 Jan 2024 20:24:45 GMT

I am guessing that perhaps you have no output destinations open and so there is nothing for ODS OUTPUT to work with. What happens if you put this command before ODS SELECT?

ods html;

But agreeing with @ballardw if that doesn't solve the problem here, and in all future problems, we need the entire LOG without macro variables, and sample data.