In the macro of a loop code, I put symbolgen mlogic mprint and this code is printing the 17000+ members that I use as filter. This prints all the 17000+ memsysid's in the saslog each time it goes through the loop and at times this will make the PC SAS windows full and I have to terminate the session. Is there a way to not let the macro print the 17000+ indiv id in the saslog. I tried using options symbolgen mlogic nomprint but this still printed the memsysid's in the saslog. Any suggestions?
Your OPTIONS statement controls SASLOG output generated by SAS - NOSOURCE NOSOURCE2 NOMACROGEN NOSYMBOLGEN NOMLOGIC NOMPRINT are possible solutions to reduce the SAS log generated. Otherwise, it's unclear what is generating the SAS log -- without sharing your SAS code. For example, you may have a DATA step that generates SAS log output using PUT or PUTLOG.
It was a success. It gave me a saslog without printing all the 17000+ individual id's that I used as filter to pull in the claims.
Thanks so much.
The other thing now is for me to know how to run the program optimmally efficient....i have a loop for the 17000+ indiv id's but am not sure if that's optimal. In the past I ran into problem that macro can hold (I think) 2000 values. Any suggestions?
Good to hear you were successful - it would be helpful to share your experience and results with the forum subscribers / viewers, for their interest and consideration. Also, for future reference, it is a more useful (and personal preferred approach) that you post code, SAS log and sample data (instream) to the forum in a post reply rather than limiting it to one individual -- since this is a general forum and not really a support help desk.