I want to suppress the display of the contents of a particular macro variable in the SAS log without turning off MPRINT.  I still want the code written to the log but not the contents of a macro variable that could hold up to 5,000 separated values (account numbers).  Is there a macro function that suppresses the display of a macro variable in the SAS log, like you might have for passwords? MPRINT(QUERY_LAST_PAYMENT_DATE): options nomgen nosgen mprint; MPRINT(QUERY_LAST_PAYMENT_DATE): proc sql; MPRINT(QUERY_LAST_PAYMENT_DATE): insert into work.output_table select a.account_number, bal_prin_amt, interest_due, extract_date,interest_paid_amt_ltd from ORACLE.TABLE1 (orhints='/*+parallel(16)*/' readbuff=1000000 where=("01DEC15:00:00:00"dt between valid_From and valid_to)) as a inner join ORACLE.TABLE2 (orhints='/*+parallel(16)*/' readbuff=1000000 where=(extract_date="01DEC15:00:00:00"dt)) as b on a.account_number=b.account_number and extract_date between valid_from and valid_to where a.account_number in ('1111111','22222','333333','44444') ; NOTE: 1 row was inserted into WORK.OUTPUT_TABLE. ... View more

I get an error when referencing an SQL view with dataset options in and SQL query;  27 proc sql; 28 create table test2 as 29 select * 30 from test_vw (where = (valid_date SYMBOLGEN: Macro variable ASATDATE resolves to 22339 30 ! = &asatdate.)) 31 ; ERROR: Unable to process SAS data set options for SQL view WORK.TEST_VW. NOTE: PROC SQL set option NOEXEC and will continue to check the syntax of statements. 32 quit; NOTE: The SAS System stopped processing this step because of errors.   If I create the view in a data step I do not get an error however it is 10 times slower as it can not exploit indexes. Also if I reference the view with dataset options in a data step there is no error.  However I was planning on replacing many very large SAS tables with SAS views without changing numerous SAS programs in production.  Many programs currently reference these tables in SQL queries with dataset options.   Does any one know how to resolve this issue in the SAS view?  Resolving the issue in the SAS programs using the views is not an option as that would require changes to numerous programs.   ... View more