SAS/ACCESS 9.2 for Relational Databases: Reference, Fourth Edition

528 Non-Libref Connections 4 Chapter 16Table 16.10Librefs and Their Authorization ImplicationsClient Sessionlibname local v8 ’SAS.data.library’disp=old;libname dblocal db2connection=unique;libname remote ’SAS.data.library’server=serv1 rengine=v8roptions=’disp=old’;libname dbremote server=serv1rengine=db2roptions=’connection=unique’;These statements execute in the client session. theseare local assignments. The authority ID is the ID of theclient.These statements execute in the server session on behalfof the client. Libref Remote is a Base SAS engineremote assignment. Libref DbRemote is a DB2 engineremote assignment. In both cases, the authority ID isthe ID of the client.Server Session (id=serv1)libname predef v8 ’SAS.data.library’disp=old;libname dbpredef db2connection=unique;Because librefs PreDef and DbPreDef are defined in theserver session, they can be referenced only by a clientusing a logical LIBNAME statement. There is noauthority ID because clients cannot access these librefsdirectly.Logical Assignments - Client Sessionlibname alias (local);libname dbalias (dblocal);libname logic server=serv1slibref=predef;libname dblogic server=serv1slibref=dbpredef;These statements create aliases ALIAS and DBALIASfor librefs Local and DbLocal, which were assigned inthe client session above. The authority ID is the ID ofthe client.These statements refer to librefs PreDef and DbPreDef,which were assigned in the server session above.Libref Logic is a Base SAS engine logical assignment ofremote libref PreDef. The authority ID for libref Logic isthe ID of the client.Libref DbLogic is a DB2 engine logical assignment ofremote libref DbPreDef. The authority ID for librefDbLogic is the ID of the server.For the Base SAS engine Remote and Logic librefs, the authority that is verified isthe client’s. (This is true for all Base SAS engine assignments.) Although the DB2engine librefs DbRemote and DbLogic refer to the same resources, the authority verifiedfor DbRemote is that of the client, whereas the authority verified for DbLogic is that ofthe server. When using SAS/ACCESS Interface to DB2 under z/OS, you can determinewhose authority (client or server) is used to access DB2 data.Non-Libref ConnectionsWhen you make connections using the SQL pass-through facility or view descriptors,the connections to the database are not based on a DB2 engine libref. A connection thatis created in the server, by using these features from a client, always has the authorityof the client, because there is no server-established connection to reference.This example uses the SAS/SHARE Remote SQL pass-through facility. The client hasits own authority for the connections.1 In the server session: