It is good practice to add a run; or quit after each procedure as appropriate. Data Steps and most procedures end with run; but a few procedures end with quit INSTEAD OF run; notably PROC SQL, PROC DATASETS, and PROC PLOT. An implied run exists when SAS encounters a procedure boundary that would include the next procedure, so if you have a lot of code it may not be essential to add the run or quit statements, but it is still good programming practice to do so. I don't believe that there are any situations where you need both a run and a quit; it is an either-or scenerio.

-Mary

----- Original Message ----- From: "Bachenot2" <Michael.F.Murphy@SCE.COM> To: <SAS-L@LISTSERV.UGA.EDU> Sent: Thursday, June 04, 2009 3:36 PM Subject: Adding "Run;" and "Quit;" Statements to Mainframe Progams Brought into UNIX

> Hi All, > We are moving a large number of mainframe SAS programs to the UNIX > environment. The mainframe data steps often do not have a "run;" > statement at the end. Queries often do not have a "quit;" statement at > the end. > My question is: what standards are appropriate for adding Run;" and > "Quit;" statements? Obviously we do not want to spend considerable > time adding these statements when it is not necessary. Much of the > work will be done using SAS Enterprise Guide, and we went to make sure > the code runs efficiently and correctly.