here is the log: NOTE: SAS Initialization used (Total process time): real time 0.00 seconds cpu time 0.00 seconds NOTE: The autoexec file, /opt/sas/config/Lev1/SASApp/WorkspaceServer/autoexec.sas, was executed at server initialization. ERROR: The submitted line exceeds maximum line length - 32768 bytes. 1 ;*';*";*/;quit;run; NOTE: SAS set option OBS=0 and will continue to check statements. This might cause NOTE: No observations in data set. NOTE: PROCEDURE PRINTTO used (Total process time): real time 0.04 seconds cpu time 0.05 seconds NOTE: Libref MSSQLLIB was successfully assigned as follows: Engine: ODBC Physical Name: mssqldynamics NOTE: Libref LASRLIB was successfully assigned as follows: Engine: SASIOLA Physical Name: SAS LASR Analytic Server engine on local host, port 10031 NOTE: The "<>" operator is interpreted as "not equals". NOTE: SQL view WORK.TEMP_LASR_VIEW_5834 has been defined. NOTE: PROCEDURE SQL used (Total process time): real time 0.04 seconds cpu time 0.05 seconds NOTE: A GROUP BY clause has been discarded because neither the SELECT clause nor the optional HAVING clause of the associated table-expression referenced a summary function. 2 The SAS System 13:08 Friday, October 17, 2014 NOTE: A GROUP BY clause has been discarded because neither the SELECT clause nor the optional HAVING clause of the associated table-expression referenced a summary function. NOTE: A GROUP BY clause has been discarded because neither the SELECT clause nor the optional HAVING clause of the associated table-expression referenced a summary function. NOTE: A GROUP BY clause has been discarded because neither the SELECT clause nor the optional HAVING clause of the associated table-expression referenced a summary function. NOTE: A GROUP BY clause has been discarded because neither the SELECT clause nor the optional HAVING clause of the associated table-expression referenced a summary function. NOTE: A GROUP BY clause has been discarded because neither the SELECT clause nor the optional HAVING clause of the associated table-expression referenced a summary function. NOTE: A GROUP BY clause has been discarded because neither the SELECT clause nor the optional HAVING clause of the associated table-expression referenced a summary function. NOTE: A GROUP BY clause has been discarded because neither the SELECT clause nor the optional HAVING clause of the associated table-expression referenced a summary function. NOTE: A GROUP BY clause has been discarded because neither the SELECT clause nor the optional HAVING clause of the associated table-expression referenced a summary function. NOTE: A GROUP BY clause has been discarded because neither the SELECT clause nor the optional HAVING clause of the associated table-expression referenced a summary function. NOTE: A GROUP BY clause has been discarded because neither the SELECT clause nor the optional HAVING clause of the associated table-expression referenced a summary function. NOTE: A GROUP BY clause has been discarded because neither the SELECT clause nor the optional HAVING clause of the associated table-expression referenced a summary function. NOTE: The query requires remerging summary statistics back with the original data. NOTE: The data set LASRLIB.ISALESOVERALL_BF has 0 observations and 36 variables. WARNING: Data set LASRLIB.ISALESOVERALL_BF was not replaced because this step was stopped. NOTE: DATA statement used (Total process time): real time 6.85 seconds cpu time 0.92 seconds INFO: Registering A5KIUB9E.BF00068J to /Shared Data/SAS Visual Analytics/Public/Visual Analytics Public LASR library. NOTE: PROCEDURE METALIB used (Total process time): real time 0.00 seconds cpu time 0.00 seconds NOTE: Line generated by the invoked macro "REGISTERTABLE". 2 omr ( library="&LIBRARY." &REPOSARG. ); ___ 180 ERROR 180-322: Statement is not valid or it is used out of proper order. NOTE: Line generated by the invoked macro "REGISTERTABLE". 2 select ("&SELECTOBJ."); ______ 180 ERROR 180-322: Statement is not valid or it is used out of proper order. 3 ;*';*";*/;quit;run; 4 QUIT; RUN;
... View more