When you use SCL code and you connect to the MySQL database with SAS/ACCESS Interface to MySQL, the SCL code does not pass a formatted date to MySQL. Instead, it passes a number to the database.

If you have two or more WHERE clauses in the SCL, no error is returned but resulting data will not be correct. You can see the problem is you use the SASTRACE= option for tracing, as shown in this example:

29   options sastrace=',,,d' sastraceloc=saslog nostsuffix;
30   /* Execute SCL program */
31   proc display c=scl.mysql.error.scl;
32   run;

MYSQL_1: Executed: on connection 2
SELECT * FROM `_GEDTEST` where (0)
dsid=1
rc=0
MYSQL_2: Executed: on connection 2
SELECT  `char`, `x`  FROM `_GEDTEST`  WHERE  ( `x` = CAST('2008-01-01' AS DATE)
)
rcf=0
rc=-580017
rc=0
MYSQL_3: Executed: on connection 2
SELECT  `char`, `x`  FROM `_GEDTEST`  WHERE  ( `x` = 17533 )
rcf=-1

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for SAS 9.1.3 (9.1 TS1M3) for this issue is available at:

A fix for SAS 9.1.3 (9.1 TS1M3) with Asian Language Support (DBCS) for this issue is available at: