topic Re: explanation of this error message in SAS Enterprise Guide

explanation of this error message

Gick — Tue, 22 Feb 2022 11:53:06 GMT

%macro gick();
%let last= eat travel;
		%do l = 1 %to 2;
			proc freq data = dat_essai noprint;
			tables dates / out = compil;
			%if &l. = 1 %then /*The problem is in this line. It does not recognize &l. as a numeric value*/
                    %do;
				where I = 1 ;
			        %end;
			%if &l. = 2 %then
                    %do;
				where I >=3;
			        %end;
			run; 

			data compil;
			set compil;
			rename count = "%scan(&last.,&l.,' ')"n;
			keep dates count;
			run;

Hello,

When I run this code, I get this error message.
I saw this message in the forum and I tried to adjust, adapt my code to report the solutions I saw on the forum. But, it still does not work. I ask for a detailed explanation of what this problem is and how can I solve it.

Thank you for your help

Gick

Re: explanation of this error message

PaigeMiller — Tue, 22 Feb 2022 12:22:33 GMT

If you open a brand new SAS session and run this code, do you still get the error?

If so, please turn on the macro debugging options

options mprint symbolgen mlogic;

then run the code again.

Please show us the entire LOG for this macro (that's 100% of the log, every single line, not selected portions) by copying the log as text and pasting it into the window that appears when you click on the </> icon.

Re: explanation of this error message

ballardw — Tue, 22 Feb 2022 15:53:12 GMT

You do not show a %mend statement to end the definition of the macro.

You do not show a matching %end for the %do l=1 %to 2 loop

You also do not show any call to that macro.

Note that use of code such as this, especially in a macro with loops,

data compil;
set compil;

is subject to all sorts of runtime value related errors and may mean the results are not what you think.

If the only purpose of a data step is to rename variables then use Proc Datasets. It will not change values if there is a hiccup and if the data set is large Proc Datasets will execute much faster as it only affects the data set header information where the variable names, formats, labels and such are stored. A data step has to process every record.

Re: explanation of this error message

Reeza — Tue, 22 Feb 2022 20:27:04 GMT

Would a format be more usable here than a macro?

proc format;
value I_fmt
1 = "eat"
3 - high = "travel"
other = 'exclude';
run;

proc freq data=dat_essai ...;
table I*dates / out=compil;
format l I_fmt.;
run;

Re: explanation of this error message

Tom — Wed, 23 Feb 2022 01:28:42 GMT

Either you have some strange character in your code that is confusing %IF.

Or there is something you aren't showing that is changing the value of the L macro variable.

Perhaps just re-typing the code will clear it up?

You could clean up the formatting and perhaps use more descriptive macro variable names while at it. Make sure the define local macro variables as local. It will not prevent macros you call from messing up their values but it will prevent this macro from messing up the values of macro variables that are being used by the code that is calling this macro.

%macro gick();
%local last index name where ;
%let last= eat travel;
%do index = 1 %to 2;
  %let name=%qscan(&last,&index,%str( ));
  %let name=%sysfunc(nliteral(&name));
  %if &index=1 then %let where=(I=1);
  %else %let where=(I>=3);

proc freq data = dat_essai ;
  where &where ;
  tables dates / noprint out=compil(drop=percent rename=(count=&name));
run; 

%end;
%mend gick;

Re: explanation of this error message

Tom — Wed, 23 Feb 2022 01:33:08 GMT

Why bother using name literals if the list of names is just space delimited? Are the names in the list not valid SAS names? If they aren't then perhaps you should not be using space as the delimiter in the list of names since some of the names might contain spaces. Also why are you asking %SCAN() to use both space and single quotes as the delimiter characters? Are there really single quotes in the list of names? And if so did you really mean for them to be treated the same as the spaces when scanning?

Re: explanation of this error message

Gick — Wed, 23 Feb 2022 03:53:16 GMT

Hello,

Here is the Log :

MLOGIC(gick) : %LET (le nom de la variable est LAST)
MLOGIC(gick) : %DBoucle DO démarrée ; variable indice L; valeur de départ : 1; valeur de fin : valeur de fin : 2;
valeur by : 1.
ERROR: A character operand was found in the %EVAL function or %IF condition where a numeric operand is required. The condition was:
&l. = 1
ERROR: The macro gick will stop executing.
MPRINT(gick): where I =
MLOGIC(gick) : Fin de l'exécution.
27
28 GOPTIONS NOACCESSIBLE;
29 %LET _CLIENTTASKLABEL=;
30 %LET _CLIENTPROCESSFLOWNAME=;
31 %LET _CLIENTPROJECTPATH=;
32 %LET _CLIENTPROJECTPATHHOST=;
33 %LET _CLIENTPROJECTNAME=;
34 %LET _SASPROGRAMFILE=;
WARNING: The quoted string currently being processed has become more than 262 characters long. You might have unbalanced quotation
marks.
35 %LET _SASPROGRAMFILEHOST=;
36
37 ;*';*";*/;quit;run;
38 ODS _ALL_ CLOSE;
39
40
41 QUIT; RUN;

Re: explanation of this error message

Tom — Wed, 23 Feb 2022 04:11:23 GMT

It is not a good idea to use both L and i as names of macro variables in the same program.

A lower case L looks a lot like an uppercase i .

Your %DO loop is using L.

Your %IF is using i.

Plus is looks a little strange that your dataset has a variable named i. Make sure you are not getting confused and thinking that the macro variable i is the same thing as the dataset variable i.

Re: explanation of this error message

Gick — Wed, 23 Feb 2022 03:59:21 GMT

Hello,

When copying the code, I forgot to copy %mend, %end. At this level there is no problem. Everything is in order. This is the error message that appears in the log, I find it difficult to understand because the code itself is well used in the macro.

I remain open to discussion.
Gick

Re: explanation of this error message

Gick — Wed, 23 Feb 2022 04:26:28 GMT

Hello,
No , it is indeed L which is defined as a macro variable and I in capital letters is the name of the variable in the data set. I used it just in the Where statement

Re: explanation of this error message

Tom — Wed, 23 Feb 2022 04:32:56 GMT

In that case retype all of the white spaces to make sure you don't have binary zeros or other invisible characters in your program that you cannot detect in the error message.

Re: explanation of this error message

Gick — Wed, 23 Feb 2022 04:36:39 GMT

Hello,
In fact, the macro-variable "last" which has 2 words (eat, travel). The scan function returns the word to me according to the value of &L. and remove the blanks. For example %scan(&last.,1,' ')=eat, %scan(&last.,2,' ')=travel. At this level, there is no problem, the line operates normally.

It is the line %if &l=1 that I encounter a problem.

Re: explanation of this error message

Tom — Wed, 23 Feb 2022 04:57:31 GMT

The only way I can get something like %IF &x = 1 %THEN to generate that error message is if the equal sign is not an equal sign. That causes SAS to consider the whole string between %IF and %THEN as a single character expression instead of a comparison operator.

Re: explanation of this error message

Gick — Wed, 23 Feb 2022 05:35:28 GMT

I adapted and adjusted your code in relation to what I'm looking for. I have the same error message

Re: explanation of this error message

Amir — Wed, 23 Feb 2022 08:11:32 GMT

Hi @Gick,

It is strange that the log shows mprint for the where clause, but there is no sign of an mprint for the proc freq code earlier in the log. Are there more parts to the log for this macro?

My attention was drawn to the message:

WARNING: The quoted string currently being processed has become more than 262 characters long. You might have unbalanced quotation
marks.

If you have unbalanced quotes elsewhere in your code then this can cause all sorts of problems / compounding effects. Please try opening a new SAS session in which you just have the macro definition for gick and call it using %gick, with no other code in your SAS session. I expect it will fail with the missing data set, this would imply the original problem is outside your macro (e.g., unbalanced quotes), but if it fails with the same error then that implies the issue is in the macro.

Please report back by showing the log using the "</>" ("Insert Code") icon.

Kind regards,

Amir.

Re: explanation of this error message

Gick — Wed, 23 Feb 2022 08:33:24 GMT

%macro gick();
/* Importation de données*/
proc import datafile="C:\dat_essai.txt" out = tab_It replace;
getnames = yes;
delimiter =";";
run;
%let last = eat travel;
%do l = 1 %to 2;
proc freq data = tab_It noprint;
tables dates / out = compil;
%if &l. = 1 %then /*The problem is in this line. It does not recognize &l. as a numeric value*/
%do;
where I = 1 ;
%end;
%if &l. = 2 %then
%do;
where I >=3;
%end;
run;

data compil;
set compil;
rename count = "%scan(&last.,&l.,' ')"n;
keep dates count;
run;

%end;
%mend;
options mprint symbolgen mlogic;
%gick();

/*----------------------------- Another approach ----------------------------------*/
%macro herm();
/* Importation de données*/
proc import datafile="C:\dat_essai.txt" out = tab_It replace;
getnames = yes;
delimiter =";";
run;
%do l = 1 %to 2;
%if &l. = 1 %then %let her=(I =1);

%else %let her=(I >=3);
proc freq data = tab_It noprint;
where &her.;
tables dates / out = compil;
run;

data compil;
set compil;
rename count = "%scan(&last.,&l.,' ')"n;
keep dates count;
run;
%end;
%mend;
options mprint symbolgen mlogic;
%herm();

-----------------------------------------------------------------------------------------------------------------------------
Both codes work and give me the same results. However, I agree with you, the problem is therefore at the command line level. I have to look for it.

I had submitted part of my macro program and the error it generated.

Thank you.
Gick

Re: explanation of this error message

Kurt_Bremser — Wed, 23 Feb 2022 08:46:55 GMT

This WARNING:

WARNING: The quoted string currently being processed has become more than 262 characters long. You might have unbalanced quotation
marks.

can also be caused by submitting macro code without a %mend. The SAS system then keeps interpreting everything as further macro code, with all kinds of funny effects.

Whenever you encounter this message, terminate the current session and start with a new, clean one. Submit your code step by step until the message starts to appear, this will help you find the incorrect code part.

And, for the log to be really helpful to us, you MUST (as in MUST) use this button to post it:

Re: explanation of this error message

Kurt_Bremser — Wed, 23 Feb 2022 08:52:33 GMT

One other BIG hint: always start to debug your code at the top. Tolerate NO WARNING/ERROR/extraneous NOTE(*), fix each single step until it issues no such message and produces the expected result. Only then advance to the next step. Often, fixing the first issue cleans up all or most of the following issues.

(*): NOTEs like "XXX is uninitialized" or "was converted to numeric/character" or "MERGE has repeats in more than one dataset" and so on. A proper step has only NOTEs about the size of the created dataset(s) and the time it took.

Re: explanation of this error message

Gick — Wed, 23 Feb 2022 12:03:17 GMT

This code works alone. But, by associating it in my whole macro program, I get the same error
"ERROR: A character operand was found in the %EVAL function or %IF condition where a numeric operand is required. The condition was:
&I. = 1
ERROR: The macro herm will stop executing. "

I note that I rechecked the other lines of my code, it works. This line, on the other hand, generates an error message that I don't understand, so executing it alone, it works.
Thank you for your help. Explanations are welcome.
Gick

Re: explanation of this error message

Kurt_Bremser — Wed, 23 Feb 2022 12:05:00 GMT

@Gick wrote:

This code works alone. But, by associating it in my whole macro program, I get the same error

This means your existing code is wrong or so badly written that it does not lend itself to being expanded.