13.07.2015 Views

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

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

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

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

504 DB2UTIL Statements and Options 4 Chapter 16COMMIT=numberspecifies the maximum number of SQL statements to execute be<strong>for</strong>e issuing anSQL COMMIT statement to establish a synchpoint. The default is 3.ERROR=fileref |fileref.memberspecifies an external file where error in<strong>for</strong>mation is logged. When DB2 issues anerror return code, the procedure writes all relevant in<strong>for</strong>mation, including the SQLstatement that is involved, to this external file. If you omit the ERROR=statement, the procedure writes the error in<strong>for</strong>mation to the <strong>SAS</strong> log.LIMIT=numberspecifies the maximum number of SQL statements to issue in an execution of theprocedure. The default value is 5000. If you specify LIMIT=0, no limit is set. Theprocedure processes the entire data set regardless of its size.SQLIN=fileref | fileref.memberspecifies an intermediate SQL output file that is created by a prior execution ofPROC DB2UTIL by using the SQLOUT= option. The file that is specified bySQLIN= contains SQL statements to update a DB2 table. If you specify an SQLIN=file, then the procedure reads the SQL statements and executes them in line mode.When you specify an SQLIN= file, DATA=, TABLE=, and SQLOUT= are ignored.SQLOUT=fileref | fileref.memberspecifies an external file where the generated SQL statements are to be written.This file is either a z/OS sequential data set or a member of a z/OS partitioneddata set. Use this option to update or delete data.When you specify the SQLOUT= option, the procedure edits your specifications,generates the SQL statements to per<strong>for</strong>m the update, and writes them to theexternal file <strong>for</strong> later execution. When they are input to the later run <strong>for</strong>execution, the procedure passes them to DB2.SSID=subsystem-namespecifies the name of the DB2 subsystem that you want to access. If you omitDB2SSID=, the subsystem name defaults to DB2. See “Settings” on page 514 <strong>for</strong>more in<strong>for</strong>mation.MAPTO StatementMAPTO <strong>SAS</strong>-name-1=DB2-name-1;The MAPTO statement maps the <strong>SAS</strong> variable name to the DB2 column name. Youcan specify as many values in one MAPTO statement as you want.RESET StatementRESET ALL | <strong>SAS</strong>-name | COLS;Use the RESET statement to erase the editing that was done to <strong>SAS</strong> variables orDB2 columns. The RESET statement can per<strong>for</strong>m one or more of these actions:ALLresets all previously entered map and column names to default values <strong>for</strong> theprocedure.<strong>SAS</strong>-nameresets the map entry <strong>for</strong> that <strong>SAS</strong> variable.COLSresets the altered column values.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!