@Riana,   Please add these options at the top of your SAS program, run it again and show me full SAS log:   options fullstimer source source2 msglevel=i mprint notes; options sastrace=",,,dsa" sastraceloc=saslog nostsuffix;   ... View more

@Riana,   The problem occurs because the ODBC driver by default does not use quoting for table names. To resolve the problem, do the following:   Enable EnableQuotedIdentifers in the ODBC driver entry. If you are on a UNIX system, you can add EnableQuotedIdenitifers=1 to the odbc.ini file. If you are on a Windows system, select Enable Quoted Identifiers on the Advanced tab of your ODBC driver entry as shown below.   ... View more

@xiaoys0725,   Yes, that should work. And, is there a way to stop a session by REST api?  /cas/sessions/terminate - terminates all user sessions by performing kill -9 on the session processes /cas/sessions/{sessionId}/cancel - ends the specified session using a cancelSession action /cas/sessions/{sessionId}/terminate - ends the specified session by performing a kill -9 on all of the session’s processes CAS REST API ... View more

@xiaoys0725,   If you are doing the SAS Viya deployment from scratch,  the web server will be running on HTTP and HTTPS ports. I'm not sure about PDC image, but most likely HTTPS is the only protocol available there. ... View more

@xiaoys0725,   Terminate a session only after having tried canceling a session. Using terminate might not release resources (for example, mapped memory and memory involving database connections, and so on). ... View more

@Sm6.   With schedule.sh you can add an entry that will start runsas.sh every X minute. By default 15. If you want to start the autoload process everyday at 17:00 you have to add this entry to the crontab: 0 17 * * * /sas/config/Lev1/Applications/SASVisualAnalytics/VisualAnalyticsAdministrator/runsas.sh ... View more

@Sm6,   That's easy. Just run this command: crontab -e   And add: 0 17 * * * /PATH/TO/AUTOLOAD/SCRIPTS/FOLDER/runsas.sh ... View more

@HULK,   I'm almost sure that this error has been generated by Base SAS started directly from Linux console. Try to use this option when you start Base SAS: -odsgraphics off ... View more

@osmelbrito,   On the server where you starting SAS session that connects to Hadoop. In your case Windows. ... View more

@efd-hkg,   It does not seem to have an effect, when I do the things as you suggest. Your compute tier and your middle tier (where SAS Visual Analytics is deployed) are on the same physical machine? If they are on different machines and they are using the same operating system, then extra steps are required to enable auditing. For details, see the topic "Deployment Topology Considerations" in the SAS Visual Analytics Administration Guide. If your compute tier and your middle tier are on different physical machines, and they are using different operating systems, then auditing is not supported. ... View more

@osmelbrito,   Sure, you can access Hadoop from SAS on Windows. JAR files has to be located in SAS_HADOOP_JAR_PATH. ... View more

@osmelbrito,   Check this document SAS® 9.4 Hadoop Configuration Guide for Base SAS® and SAS/ACCESS®, Fourth Edition especially Appendix 1 Using the SAS Deployment Manager to Obtain Hadoop JAR and Configuration Files ... View more