When SAS^® software encounters an invalid comment in the SAS configuration file at initialization, the SAS System fails to initialize and issues the following error message in the JES Log, causing the job to fail with a S000 abend:

BPXP018I THREAD nnnnnnnnnnnnnnnn, IN PROCESS nnnnnn, ENDED
WITHOUT BEING UNDUBBED WITH COMPLETION CODE 000003E7, AND REASON CODE
00000000.
BPXP018I THREAD 1FC4141000000000, IN PROCESS nnnnnn, ENDED
WITHOUT BEING UNDUBBED WITH COMPLETION CODE 040003E7, AND REASON CODE
00000000.

The following error message might appear as well:

ERROR:      OPTION NOT RECOGNIZED -

The following SAS configuration files are available to the SAS System:

1. Batch processing CONFIG files:

DBATW0 --> DBCS support
BATW0  --> non-DBCS support
BATESW0 --> Spanish support
BATFRW0 --> French support

2. Interactive processing CONFIG files:

DTSOW0 --> DBCS support
TSOW0  --> non-DBCS support
TSOESW0 --> Spanish suport
TSOFRW0 --> French Support

To circumvent these errors, check the contents of your configuration file to ensure that any comments start with an asterisk in column one. For example, if your SAS session points to the BATCH member of your prefix.CNTL installation file that contains the following comment (which is invalid), the SAS System will fail as noted above:

Operating System and Release Information