The SAS Output Delivery System and reporting techniques

Inforrmation needed about Quit statement.

Reply
Contributor msg
Contributor
Posts: 21

Inforrmation needed about Quit statement.

Hi all,

Unlike "run", certain procesures like proc sql, datasets use "quit" statement to end their step. Every document specifies that they are "interactive" procedures which ic different from other proc's. So, my question is "in what way are they different?". Can we visualize this by an example code?

Thanks
Msg
Super Contributor
Super Contributor
Posts: 3,174

Re: Inforrmation needed about Quit statement.

Any of these PROCs have commands that can be executed depending on the specific requirement, such as PROC DATASETS or PROC CATALOG - you can review the SAS Procedures Guide for the commands related to the procedure. And so the given procedure remains in a "running" state (depending on the OS platform and whether executing in batch or interactive) until the QUIT; command is issued. Also, for some PROCs, an allocated "libref" or "fileref" remains open until the QUIT; command is issued, which is another consideration for the command.

Scott Barry
SBBWorks, Inc.
PROC Star
Posts: 1,561

Re: Inforrmation needed about Quit statement.

Further to Scott's reply, another example of a command is a SQL statement in proc sql.
You can start proc sql, and then run SQL statements as you go. Each SQL statement is standalone within the procedure, and doesn't need anything else (like a runSmiley Wink to be executed.
A third example is proc gplot: You start it, and then do as many plots as you you want on the table the procedure uses. In this case, because a graph might need several statements, each graph is created when the run; statement is encountered.
Contributor msg
Contributor
Posts: 21

Re: Inforrmation needed about Quit statement.

Thanks Sbb & Chris, for your information.
Ask a Question
Discussion stats
  • 3 replies
  • 160 views
  • 0 likes
  • 3 in conversation