Providing software solutions since 1976

• Log in
• Create profile
• Welcome
  [Log out]
• Edit profile

• Print  |
• Feedback  |
• Share

  • E-mail

  
  
  

  E-mail This Page

  Your Name:*
  Your E-mail:*
  Recipient E-mail:*
  Send a copy to me
  Personal Message:
  
  

  * indicates a required field

Here are some of the most likely reasons why your output data set is not generated when you use the ODS OUTPUT statement:

• You used the NOPRINT option on the procedure.

  When the NOPRINT option is used on the procedure, this disables the procedure from sending the individual output objects to the ODS. To prevent output being sent to the default listing, use the ODS LISTING CLOSE statement instead.

  ods listing close;
  ods output xxx=temp;
  proc corr data=sashelp.class;
  run;
  ods listing;
  

• You omitted a RUN statement or other step boundary.

  The ODS statement is not a step boundary, so the RUN or other step boundary statement has to be supplied before the output data set can be generated. The ODS statement also needs to be placed before the step boundary. If the procedure is an interactive procedure, then the QUIT statement is also necessary.

• You requested an unavailable statistic.

  Verify that the statistic that you are requesting is the correct statistic based on the options that you have specified for the procedure. To verify that the statistic that is specified on the ODS OUTPUT statement is valid, use the ODS TRACE ON statement to dump the trace record either to the log or the listing. If the trace record does not include the statistic that you have on the ODS OUTPUT statement, then this statistic is not produced with the procedure based on the options specified.

  ods trace on / listing;
  ods listing close;
  ods output moments=temp;
  proc univariate data=sashelp.class;
  run;
  ods listing;
  

• You made a typo.

  Verify the spelling of the statistic name.

Operating System and Release Information