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

498 DBLOAD Procedure Specifics for DB2 Under z/OS 4 Chapter 16/* create vlib.usacust view */create vlib.usacust.view;select customer state zipcode namefirstorder;subset where customer like ’1%’;run;This next example uses the SERVER= statement to access the SQL/DS tableTestid.Orders from a remote location. Access and view descriptors are then createdbased on the table.libname adlib ’SAS-data-library’;libname vlib ’SAS-data-library’;proc access dbms=db2;create adlib.customr.access;table=testid.orders;server=testserver;assign=yes;list all;create vlib.allord.view;select ordernum stocknum shipto dateorderd;subset where stocknum = 1279;run;DBLOAD Procedure Specifics for DB2 Under z/OSKey InformationSee DBLOAD Procedure for general information about this feature. DB2 z/OSexamples“Examples” on page 499 are available.SAS/ACCESS Interface to DB2 under z/OS supports all DBLOAD procedurestatements in interactive line, noninteractive, and batch modes. Here are the DBLOADprocedure specifics for SAS/ACCESS Interface to DB2 under z/OS.3 The DBMS= value is DB2.3 Here are the database description statements that PROC DBLOAD uses:SSID=DB2-subsystem-idspecifies the DB2 subsystem ID to connect to at connection time. SSID= isoptional. If you omit it, SAS connects to the DB2 subsystem that is specifiedin the SAS system option, DB2SSID=. The DB2 subsystem ID is limited tofour characters. See “Settings” on page 514 for more information.SERVER=DRDA serverspecifies the DRDA server that you want to connect to. SERVER= enablesyou to access DRDA resources stored at remote locations. Check with yoursystem administrator for system names. You can connect to only one serverper LIBNAME statement.