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

SAS/ACCESS Interface to DB2 Under z/OS 4 Arguments 485DB2 Attachment Facilities (CAF and RRSAF) 531Accessing DB2 System Catalogs 532Introduction to SAS/ACCESS Interface to DB2 Under z/OSThis section describes SAS/ACCESS Interface to DB2 under z/OS. For a list ofSAS/ACCESS features that are available in this interface, see “SAS/ACCESS Interfaceto DB2 Under z/OS: Supported Features” on page 77.Note: z/OS is the successor to the OS/390 (formerly MVS) operating system. SAS9.1 for z/OS is supported on both OS/390 and z/OS operating systems and, throughoutthis document, any reference to z/OS also applies to OS/390 unless otherwise stated. 4LIBNAME Statement Specifics for DB2 Under z/OSOverviewThis section describes the LIBNAME statement that SAS/ACCESS Interface to DB2under z/OS supports and includes an example. For details about this feature, see“Overview of the LIBNAME Statement for Relational Databases” on page 87.Here is the LIBNAME statement syntax for accessing DB2 under z/OS interface.LIBNAME libref db2 ;Argumentslibrefspecifies any SAS name that serves as an alias to associate SAS with a database,schema, server, or group of tables and views.db2specifies the SAS/ACCESS engine name for the DB2 under z/OS interface.connection-optionsprovides connection information and control how SAS manages the timing andconcurrence of the connection to the DBMS. Here is how these options are defined.LOCATION=locationmaps to the location in the SYSIBM.LOCATIONS catalog in thecommunication database. In SAS/ACCESS Interface to DB2 under z/OS, thelocation is converted to the first level of a three-level table name:location.authid.table. DB2 Distributed Data Facility (DDF) CommunicationDatabase (CDB) makes the connection implicitly to the remote DB2subsystem when DB2 receives a three-level name in an SQL statement.If you omit this option, SAS accesses the data from the local DB2 databaseunless you have specified a value for the SERVER= option. This option is notvalidated until you access a DB2 table. If you specify LOCATION=, you mustalso specify the AUTHID= option.SSID=DB2-subsystem-id