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

466 Configuring DB2 EEE Nodes on Physically Partitioned Databases 4 Chapter 15Optimization of the threaded read against this partitioned table depends upon thelocation of the DB2 partitions. If the DB2 partitions are on the same machine, you canuse DBSLICE= with the DB2 NODENUMBER function in the WHERE clause:proc print data=trlib2.MYEMPS(DBSLICE=("NODENUMBER(EMPNO)=0""NODENUMBER(EMPNO)=1" "NODENUMBER(EMPNO)=2"));run;If the DB2 partitions reside on different physical machines, you can usually obtainthe best results by using the DBSLICE= option with the SERVER= syntax in additionto the DB2 NODENUMBER function in the WHERE clause.In the next example, DBSLICE= contains DB2-specific partitioning information.Also, Sample3a, Sample3b, and Sample3c are DB2 database aliases that point toindividual DB2 EEE database nodes that exist on separate physical machines. Formore information about the configuration of these nodes, see “Configuring DB2 EEENodes on Physically Partitioned Databases” on page 466.proc print data=trlib2.MYEMPS(DBSLICE=(sample3a="NODENUMBER(EMPNO)=0"samble3b="NODENUMBER(EMPNO)=1" sample3c="NODENUMBER(EMPNO)=2"));run;NODENUMBER is not required to use threaded reads for SAS/ACCESS Interface toDB2 under UNIX and PC Hosts. The methods and examples described in DBSLICE=work well in cases where the table you want to read is not stored in multiple partitionsto DB2. These methods also give you full control over which column is used to executethe threaded read. For example, if the STATE column in your employee table containsonly a few distinct values, you can tailor your DBSLICE= clause accordingly:data work.locemp;set trlib2.MYEMPS (DBSLICE=("STATE=’GA’""STATE=’SC’" "STATE=’VA’" "STATE=’NC’"));where EMPNUM