Date: Sun, 24 Oct 2004 20:19:14 -0700
Reply-To: Avram Aelony <aavram@MAC.COM>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Avram Aelony <aavram@MAC.COM>
Subject: Re: Compile & Run JCL.
Content-Type: text/plain; charset=US-ASCII; format=flowed
I like to use the rule of thumb that a piece of code is "compiled" if
it is independently executable on the operating system it was compiled
on (it may also need "linked" properly). Thus it no longer needs the
helper (compiler) program to produce results. Compile-time also
usually occurs independently of run-time. This is not a precise
definition, but it works for me.
On Oct 22, 2004, at 7:42 AM, Lustig, Roger wrote:
> What would you call a view? A compiled macro? Compiled SCL? Those
> aren't load modules--they all need to be used within the SAS
> environment, controlled by the SAS supervisor--but they're certainly
> Your statement is correct if "the same sense as an assembler or Cobol
> program" is taken strictly. But even those need a certain
> environment, linking, etc. before they can run.
> For that matter, one could argue that a format in a library is
> -----Original Message-----
> From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU]On Behalf Of
> Dennis Diskin
> Sent: Friday, October 22, 2004 10:35 AM
> To: SAS-L@LISTSERV.UGA.EDU
> Subject: Re: Compile & Run JCL.
> SAS is an INTERPERTED language. It does not get compiled in the same
> sense as an assembler or Cobol program. There is no way to generate a
> load module.
> Dennis Diskin
> Narra <nrkanna@BLUEBOTTLE.COM> wrote:
> Hi All,
> I wish to run my SAS programs as Load Modules. So, i tried to
> execute the JCL which is available at Xephon Archives that processes
> EXECUMON SMF records. I think, in that example, they are coding SAS
> program along with the Assembler and therefore, they are using ASMBLR
> Can you pls. pass on the JCL to COMPILE and RUN a pure SAS program?.
> Hope there should be different execs here.
> Thanks in anticipation.