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

SAS/ACCESS Interface to DB2 Under z/OS 4 Libref Connections 527Understanding DB2 Under z/OS Client/Server AuthorizationLibref ConnectionsWhen you use SAS/ACCESS Interface to DB2 under z/OS, you can enable each clientto control its own connections using its own authority (instead of sharing connectionswith other clients) by using the DB2 Recoverable Resource Manager Services AttachmentFacility (RRSAF). See DB2 Attachment Facilities (CAF and RRSAF)“DB2 AttachmentFacilities (CAF and RRSAF)” on page 531 for information about this facility.When you use SAS/ACCESS Interface to DB2 under z/OS with RRSAF, theauthorization mechanism works differently than it does in Base SAS:3 In Base SAS, the SAS server always validates the client’s authority beforeallowing the client to access a resource.3 In SAS/ACCESS Interface to DB2 under z/OS (with RRSAF), DB2 checks theauthorization identifier that is carried by the connection from the SAS server. Inmost situations, this is the client’s authorization identifier. In one situation,however, this is the SAS server’s authorization identifier. A client can access aresource by using the server’s authorization identifier only if the client uses a librefthat was predefined in the server session.In this next example, a user assigns the libref SRVPRELIB in the SRV1 serversession. In the client session, a user then issues a LIBNAME statement that makes alogical assignment using the libref MYPRELIB, and the user specifies the LIBNAMEoption SERVER=srv1. The client can then access resources by using the server’sauthority for the connection.1 In the server sessionlibname srvprelib db2 ssid=db25;proc server id=srv1;run;2 In the client sessionlibname myprelib server=srv1 slibref=srvprelib;proc print data=myprelib.db2table;run;In this example, because the client specifies a regular libref, MYDBLIB, the clienthas its own authority for the connections.1 In the server sessionlibname myprelib db2 ssid=db25;proc server id=srv1;run;2 In the client sessionlibname mydblib server=srv1 roptions=’ssid=db25’ rengine=db2;proc print data=mydblib.db2table;run;In this table, SAS/SHARE clients use LIBNAME statements to access SAS librariesand DB2 data through the server. In this description, a logical LIBNAME statement isa statement that associates a libref with another libref that was previously assigned.