BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
odesh
Quartz | Level 8

Hello,

I have a question on ``Overview of SAS® In-Memory Analytics and the Code Accelerator for Hadoop`. Please see the attached print screen. I understand that the library definition AHDLSR is used to provide the connection to the LASR session. BUt I do not see why the SASIOLA engine is not used  ( cannot  be used ? )  to access the in- memory AHDLSR.customerorders table. What advantage is there in this approach ?

 

Thanks.

Odesh.

1 ACCEPTED SOLUTION

Accepted Solutions
Cynthia_sas
Diamond | Level 26

Hi:
  The course instructors recommend that you look a bit earlier in the same video...approximately time stamp 00:10 where you can see that the SASIOLA engine IS used for the AHDLSR library:

sasiola_is_used.png

 

 Then, there is a longer explanation too. The instructors said that

"There are really two sessions. The SAS Workspace server session (or some kind of SAS session) and the LASR session. So the LIBNAME statement that defines the SASIOLA library is really defining the SASIOLA library for the Workspace server so it can connect to the LASR server and make the request to the LASR server to run a process on an in-memory table.

AHDLSR is the SASIOLA library. You can see it in the full code but it is not shown on the slide. The slide you posted does not show the LIBNAME statement.

Here is the SASIOLA libname statement in the program from time stamp 00:10:
libname AHDLSR sasiola
        port=&lasrport
        host='server2.demo.sas.com'
        tag="USER.&std..DIACHD.HPAdata";

This library is defined for the SAS session and it tells the SAS session how to connect to the LASR server session where a table called customerorders has been loaded into memory. It also defines a tag for the AHDLSR library. So this library will only allow the user of the SAS session to access in memory tables that have the tag "USER.STUDENT.DIACHD.HPADATA" (&std resolves to STUDENT). The customerorders table does have that tag as part of it’s name.

So when you submit the IMSTAT procedure in the SAS session it uses the SASIOLA libname statement to connect to the LASR server and tells the LASR server to run a process on the LASR server. The LASR server uses the in memory customerorders table because that is the table identified by AHDLASR.CUSTOMERORDERS.

One could say, as shown by the note in the slide you posted, that the SASIOLA library is not used by the LASR server. But that is because the SASIOLA library is really defined to the SAS session only, for the purpose explained above and as shown with the LIBNAME statement."

 

Hope this helps,

Cynthia

View solution in original post

2 REPLIES 2
Cynthia_sas
Diamond | Level 26

Hi:
  The course instructors recommend that you look a bit earlier in the same video...approximately time stamp 00:10 where you can see that the SASIOLA engine IS used for the AHDLSR library:

sasiola_is_used.png

 

 Then, there is a longer explanation too. The instructors said that

"There are really two sessions. The SAS Workspace server session (or some kind of SAS session) and the LASR session. So the LIBNAME statement that defines the SASIOLA library is really defining the SASIOLA library for the Workspace server so it can connect to the LASR server and make the request to the LASR server to run a process on an in-memory table.

AHDLSR is the SASIOLA library. You can see it in the full code but it is not shown on the slide. The slide you posted does not show the LIBNAME statement.

Here is the SASIOLA libname statement in the program from time stamp 00:10:
libname AHDLSR sasiola
        port=&lasrport
        host='server2.demo.sas.com'
        tag="USER.&std..DIACHD.HPAdata";

This library is defined for the SAS session and it tells the SAS session how to connect to the LASR server session where a table called customerorders has been loaded into memory. It also defines a tag for the AHDLSR library. So this library will only allow the user of the SAS session to access in memory tables that have the tag "USER.STUDENT.DIACHD.HPADATA" (&std resolves to STUDENT). The customerorders table does have that tag as part of it’s name.

So when you submit the IMSTAT procedure in the SAS session it uses the SASIOLA libname statement to connect to the LASR server and tells the LASR server to run a process on the LASR server. The LASR server uses the in memory customerorders table because that is the table identified by AHDLASR.CUSTOMERORDERS.

One could say, as shown by the note in the slide you posted, that the SASIOLA library is not used by the LASR server. But that is because the SASIOLA library is really defined to the SAS session only, for the purpose explained above and as shown with the LIBNAME statement."

 

Hope this helps,

Cynthia

odesh
Quartz | Level 8
Thanks . Very good explanations ( both short and long )