topic Re: Getting error in log in SAS Procedures

Getting error in log

brophymj — Fri, 24 Jul 2015 15:31:52 GMT

Within my sas program I call another program where one of the datasets contains the code:

%let enddt=%sysfunc(inputn(&exposurecutoff,yymmdd8.)); /* converting to sas date */

if (year(start) ge &exposureyearstart) and (year(end) le year(&enddt));

This works perfectly when I run the first program and open the second program manually and running it (rather than calling it using %include). When I run the first program which calls the second one using %include I get the following error:

1008 +if (year(start) ge &exposureyearstart) and (year(end) le

1008!+year(&enddt));

WARNING: Apparent symbolic reference ENDDT not resolved.

ERROR 22-322: Syntax error, expecting one of the following: a name,

a quoted string, a numeric constant,

a datetime constant, a missing value, ), INPUT, PUT.

This has to be due to the fact that I'm calling it the program.

Re: Getting error in log

Reeza — Fri, 24 Jul 2015 15:39:22 GMT

Check the length of the line in the program, if it's over 256 characters it causes issues. Use LRECL to set the length.

%include 'program1.sas' /lrecl=300;

Re: Getting error in log

brophymj — Fri, 24 Jul 2015 15:48:23 GMT

the length of the line is if (year(start) ge &exposureyearstart) and (year(end) le year(&enddt)); which is less than 256 characters

Re: Getting error in log

Doc_Duke — Fri, 24 Jul 2015 16:27:56 GMT

Is line 1008 in the same macro as the %LET for enddt? If not, you may need to define it as a global.

Re: Getting error in log

Ron_MacroMaven — Fri, 24 Jul 2015 21:26:39 GMT

add the following information notes

%put info &=exposurecutoff;

%let enddt=%sysfunc(inputn(&exposurecutoff,yymmdd8.)); /* converting to sas date */

%put info &=exposureyearstart &=enddt;

if (year(start) ge &exposureyearstart) and (year(end) le year(&enddt));

Re: Getting error in log

Fugue — Fri, 24 Jul 2015 22:09:49 GMT

Is the code in your first program wrapped in a macro? If so, the enddt macro will be local unless you expressly declare it as global.

Re: Getting error in log

Tom — Sat, 25 Jul 2015 01:23:35 GMT

Truncation could still be your problem. The actual line that is truncated could be anywhere before line 1008 and have the effect of not running the step that creates the macro variable.

Re: Getting error in log

kaji — Mon, 26 Oct 2015 12:21:45 GMT

HI,

I found a pretty cool add-in to Base SAS on www.tatesoft.com that may be very usefull to you. The tool called Log Analyser is integrated into Base SAS and can produce Log summary report in a second. You may also analyse log in details if you wish. Really great tool!