Date:         Fri, 10 Sep 1999 06:53:10 -0500
Reply-To:     "FONTAINE, JIMI" <JIMI.FONTAINE@INFORES.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         "FONTAINE, JIMI" <JIMI.FONTAINE@INFORES.COM>
Subject:      Re: Stopping a PC SAS job run without ending session. endsas etc.

It s the first time I am present on SAS-L because I dicovered it a few days
ago.
I hope everybody excuse my poor english but I am not a native english and l
am a Iittle bit out of practice.

So a other way for :Stopping a PC SAS job run without ending session. endsas
is to write all your code in one unique MACRO and to use a %goto:

%MACRO  my_pgm;

code1: that you want run it;

a) %goto THE_END;  where you want break stop your pgm
and of course to write at the end of your MACRO this example of code:

code2: that you don t want run it;

b) %THE_END : %put End of this pgm;

%MEND my_pgm;


I happy to share what I know and learn what I don t.

@+
Jimi FONTAINE
--------------------------
IRI - SECODIP
PARIS - FRANCE
--------------------------

> -----Message d'origine-----
> De:   Sarah Leonard [SMTP:sleonard@SARAHLEONARD.COM]
> Date: vendredi 10 septembre 1999 13:13
> À:    SAS-L@LISTSERV.UGA.EDU
> Objet:        Re: Stopping a PC SAS job run without ending session. endsas
> etc.
>
> One of the alternative methods is to put the code segment you want to run
> in
> a macro statement and the other code in another macro segment.
>
> %macro runthis;
> code
> %mend;
> %macro norun;
> code
> %mend;
>
> and then run the code by invoking the macro.
>
> %runthis;
>
> I tend to write my code segments in macros anyway, to generalize code so
> that it can be
> re-used for different data sets with similar structures (for example,
> different years of the same data), so this works for me.
>
> Sarah
> -----Original Message-----
> From: Peter Crawford <peter.crawford@DB.COM>
> Newsgroups: bit.listserv.sas-l
> To: SAS-L@LISTSERV.UGA.EDU <SAS-L@LISTSERV.UGA.EDU>
> Date: Friday, September 10, 1999 3:41 AM
> Subject: Stopping a PC SAS job run without ending session. endsas etc.
>
>
> >sounds like you are running SAS Display Manager and
> >you don't know what happens when, in the program editor,
> >you issue the command
> >                    subtop 500
> >(g)
> >There are alternative ways of submitting just
> >a part of a program, but the method above has the effect
> >you were seeking!
> >
> >Good luck
> >Peter Crawford
> >
> >
> >Datum:         10.09.99 01:48
> >An:            SAS-L@listserv.uga.edu
> >
> >
> >
> >
> >Antwort an:    SeltzerJD@phibred.com
> >
> >Betreff:       Stopping a PC SAS job run without ending session. endsas
> etc.
> >Nachrichtentext:
> >
> >
> >
> >Suppose I have a large complex messy program and I want to
> >run the program from the start through maybe 500 lines of perhaps 100
> lines.
> >If I run it batch I can stick into the program an endsas; statement
> >at line 500 and the program will stop and get out of SAS when it sees the
> >statement, but I will still have the .log files and any .lis files
> created.
> >
> >Suppose I now am running the SAS session interactively.  Is there a
> command
> >that works almost like the endsas statement, but where the submitted job
> >ends
> >only, but I am still in my interactive SAS session?
> >
> >If I were to use the endsas; statement in the interactive session the
> >statement
> >when invoked would end the SAS job as well as the interactive SAS
> session.
> >