-1

So I am only executing a program using proc sql to create a table with statistics on X.

After a while, the task bar says complete, but the table is never created and I have this error poping up.

Any idea where it can come from? I can run other programs just fine so it's specific to that one.

Thanks!

[img]https://i.stack.imgur.com/Ia0pw.png

wimz
  • 1
  • 1
  • 3
  • Googling your title shows this might be due to your program generating an abnormally large log. Without the program itself, we can't tell you much more. – Josh Eller Jun 06 '19 at 16:41
  • The program is about 1600 lines with 1 big querie of like 800-900 lines. Is there a way to prevent printing parts of the log? – wimz Jun 06 '19 at 17:01
  • Well yeah, there's a billion and one options. To start, try putting `options nosource nonotes errors=0;` at the start of your program and see if it runs. If so, figure out what log output you need to keep and go from there. – Josh Eller Jun 06 '19 at 17:10
  • Just tried it, unfortunately i get the same error. – wimz Jun 06 '19 at 17:21
  • Like I said, we're not going to be able to do much without seeing your program. All I'm doing is googling your error message. Try cutting out pieces of it to see exactly what procedure/step is causing the error. – Josh Eller Jun 06 '19 at 17:25
  • Yeah I know, it's just as much as I'd like to paste the code, I can't (work for a bank) and it's all private stuff. Don't really want to potentially lose my job over a stupid SAS error hehe. Thanks for your help anyway. – wimz Jun 06 '19 at 17:30

1 Answers1

0

Well, I just figured it out if it helps anybody in the future.

For me, I was adding a new column with conditions like

SELECT*
,Case
    WHEN calculated columnX like 'text1' OR
         calculated columnX like 'text2' OR
         calculated columnX like 'text3' 
    THEN result
END AS columnX
FROM TableA

but the column after the calculateds should have been columnW. Basically, it was auto-referencing. It didn't gave me an error in the log, and without a debugger, it was quite hard to find.

Hope it helps.

wimz
  • 1
  • 1
  • 3
  • Doing something like that in Display Manager generates an exception and a message in the LOG to tell SAS technical support about it with a dump of some traceback information. I suspect that EG (and probably SAS/Studio) is getting confused by the failure and not returning the log messages to you. – Tom Jun 06 '19 at 19:17