Thank you @MKQueen. ... View more

@pchegoor1 , The physical path for Path-based CASLIB is located to the CAS Controller Server or a NFS drive mounted to CAS Controller server. There are two types of mechanism to load CAS (In-memory) from source data location, one is client side load and other is server side load.    The user interface which can access CAS like SAS 9.4x, SAS studio , Python  etc. are clients and data can be loaded from there too called client side load. In the client side load the data files are available and accessible from client machine only. The file transfer data connector is used in the CAS load action to load these data files.   The second one is server side load, where the data files/table available and accessible to CAS controller server and can be loaded to CAS using data connectors like PATH based CASLIB, and Database CASLIB.     To load CAS from client side data using SAS studio, user does not have to physically place the data file onto CAS Controller server. It's just different syntax and mechanism used to load data from client side. Here is an PROC CASUTIL example where a SAS datasets table being loaded into CAS. Notice the "load data= ..." statement rather than  "load casdata=..." statement .      proc casutil ;    load data=sashelp.prdsale  casout="prdsale"  ; run ;   -Uttam  ... View more

Hi  I am trying to follow this and read files in S3 bucket using the capability of Athena  but facing issues. The files in S3 are in multipart parquet format.  Here in this example you have created a table and reading that from SAS, which i understand . however in my case reading a table having parquet format files are not working. Do you have any idea on how to get this working please?. It complains about the below error ERROR: Prepare error: [Simba][AthenaJDBC](100071) An error has been thrown from the AWS Athena client. SYNTAX_ERROR: line 1:15: Schema ******** does not exist SQL statement: SELECT * FROM *******._ACTIVITY The database and schema definitely exists as i can query from AWS Athena. I am able to successfully establish the connection using the JDBC driver.  NOTE: Libref ATHENA was successfully assigned as follows: Engine: JDBC   Any info on how to fix this would be very helpful and much appreciated. ... View more

Hi    I am trying to follow this and read files in S3 bucket using the capability of Athena  but undergoing issues. The files in s3 are in multipart parquet format.   Here in this example you have created a table and reading that from SAS, which i understand . however in my case reading a table having parquet format files are not working. Do you have any idea on how to get this working please?. it complains about the below error ERROR: Prepare error: [Simba][AthenaJDBC](100071) An error has been thrown from the AWS Athena client. SYNTAX_ERROR: line 1:15: Schema ******** does not exist SQL statement: SELECT * FROM *******._ACTIVITY The database and schema definitely exists as i can query from AWS Athena. I am able to successfully establish the connection using the JDBC driver.  NOTE: Libref ATHENA was successfully assigned as follows: Engine: JDBC   Any info on how to fix this would be very helpful and much appreciated.       ... View more

Thanks Gerry  How is other way round?. like promoting from 3.5 to 3.4 . are VA reports backward compatible?.     ... View more

@Ramprakash  - You can define your Oracle connections as libraries in SAS metadata so they are available to all users. This would have the same effect as setting a global system option.  ... View more

Please note that in SAS Viya 3.4 you actually have two versions of SAS Studio. url .../SASStudioV/... this is SAS Studio 5.1 using a SAS Compute Server to run your code, it is integrated in the the application menu, top left, 3 vertical lines url .../SASStudio/... this is SAS Studio 4.4 using a SAS Workspace Server to run your code, it is not integrated with the application menu, your link mentioned refers to this   the following macros vars give you more details: %put NOTE: &=SYSVLONG; %put NOTE: &=SYSSCPL; %put NOTE: &=SYSPROCESSMODE; %put NOTE: &=SYSPROCESSNAME; %put NOTE: &=_CLIENTAPP; %put NOTE: &=_CLIENTAPPVERSION; %put NOTE: &=_CLIENTMODE; ... View more

Hello Ramprakash, Thank you for your feedback on my article. To use the CNTL= option in CASL, you would place right after the execDirect action. proc cas; fedsql.execDirect cntl={nowarn=true} /; query= " select * from TABLE3 ; " ; quit; I hope this helps. ... View more