SCL entries store SAS Component Language
(SCL) code, but they do not provide a display. The SCL programs for
FRAME entries are stored in associated SCL entries. You can also use
SCL entries to store method definitions and SCL programs that perform
tasks that do not require any user interaction. You use the BUILD
procedure's SOURCE window to edit the SCL code in SCL entries. Refer
to the
SAS Component Language: Reference for more information on the SAS Component Language
elements that you can use in SCL programs.
Before the SCL code
in an SCL entry can be executed, it must be compiled. To compile the
program, issue the COMPILE command in the SOURCE window (or in the
DISPLAY window if the code is associated with a FRAME entry). You
can also use the COMPILE statement with the PROC BUILD statement to
compile the contents of existing SCL entries.
When the source code
in an SCL entry is compiled, the SCL compiler writes any error or
warning messages to the SAS log. If no errors are encountered, a message
similar to the following is displayed:
Code generated for MYPROG. Code size=1276
However,
if there are warning messages, you see a message similar to the following:
Code generated (with messages) for MYPROG. Code size=1276
If
there are errors in your program, you see the following message:
ERROR: Compile error(s) detected. No code generated.
When you save an SCL
entry after its program is compiled successfully, the compiled code
is saved to the entry along with the source code. At this point, you
can execute the SCL entry as described in
Calling SCL Entries from Other SAS/AF Programs.
You should always compile
an entry before you save it. If you save an SCL entry without compiling
it, you cannot execute it.
SAS/AF
software provides a warning message indicating that the entry has
been saved without intermediate code.