DI-studio ERROR: A character ...The condition was: &_armrc

[Ullsokk]

I am having a strange error on a SQL join in DI-studio:

NOTE: Table WORK.W194IC3S created, with 120947637 rows and 10 columns.

802 quit;
PROCEDURE| _DISARM| STOP| _DISARM| 2021-02-18T09:46:26,191+01:00| _DISARM| WorkspaceServer| _DISARM| SAS| _DISARM| |
_DISARM| 197402624| _DISARM| 24104960| _DISARM| 11| _DISARM| 31| _DISARM| 300992697344| _DISARM| 301037863083| _DISARM| 567.296875|
_DISARM| 761.192000| _DISARM| 1929256425.000000| _DISARM| 1929257186.192000| _DISARM| 257.187500| _DISARM| | _ENDDISARM
NOTE: PROCEDURE SQL used (Total process time):
real time 12:41.19
cpu time 9:27.29

803
804 %global etls_sql_pushDown;
23 The SAS System 09:33 Thursday, February 18, 2021

805 %let etls_sql_pushDown = &sys_sql_ip_all;
806
807 %rcSet(&sqlrc);
808
809 %perfstop(metrVal6=%sysfunc(max(&etls_recnt,-1)));
MPRINT(PERFSTOP): options notes nosource nosource2 nosymbolgen nomprint nomlogic
ERROR: A character operand was found in the %EVAL function or %IF condition where a numeric operand is required. The condition was:
&_armrc
ERROR: The macro PERFSTOP will stop executing.

The error occurs after the SQL operation has run, and the output data seems to be fine, so the subsequents nodes run. I have tried deleting the entire node, inserting a new, using other datasets, and sometime the error doesn't show up after a ton of tinkering. But then it suddenly pops up again when running the entire flow.

[LinusH · Accepted solution]

I guess you have only DI Studio generated code?

It could be worth sending this to SAS tech support.

If you don't use the extesive performance monitoring (it's activated by default in DI Studio, that's why I ask), a simple solution would be to turn it off, since it seems that something goes wrong in those macros?

It is a bit hard to debug since the macro itself turns off MPRINT etc....

[Ullsokk]

Yes, only DI-generated code. 

Will look into turning off performance monitors

[Ullsokk]

Tried turning off the performance monitors, and the Error vanished.