Starting SAS and Using Syntax Checking

In the SAS invocation for the non-interactive server session, consider whether to specify syntax checking using the SYNTAXCHECK or NOSYNTAXCHECK system options.
uses additional resources to validate SAS statements while producing limited results. For example, the first instance of a syntax error triggers syntax checking, which automatically sets the value of the OBS= system option to 0. Consequently, no observations can be created by subsequent SAS statements in the program. For programs that are still under development and that might contain errors, consider using the SYNTAXCHECK option.
enables continuous processing of statements regardless of syntax error conditions. When executing debugged production programs that are unlikely to encounter errors, consider using the NOSYNTAXCHECK option.
You can specify the NOSYNTAXCHECK option when signing on to a server session on the same symmetric multi-processing (SMP) computer that the client session is running on. This option is most useful when client and server sessions run on SMP hardware. SAS invocations can be specified using the SASCMD= system option and the SASCMD= option in the RSUBMIT and in the SIGNON statements. For details, see SASCMD= System Option , RSUBMIT SASCMD= , and SIGNON SASCMD=.
Here is an example of a SAS invocation that runs on the same computer at which the client session runs:
signon smp sascmd="sas -nosyntaxcheck -noterminal";
Here is an example of a Windows command file named mysas.bat:
cd "C:\Program Files\alpair\SAS\V9.2"
mkdir mywork
sas %* -nosyntaxcheck -work "mywork"
%* adds the appended TCP/IP access method options to the SAS invocation in mysas.bat.
To execute the command file, specify its name as the value for SASCMD=.
options sascmd="mysas.bat";
For details about the NOSYNTAXCHECK and NOTERMINAL system options, see SAS System Options: Reference.