An associative array of connection options that affect the behavior
       of the connection, where valid array keys include:
       
       The following new option is available in ibm_db2 version 1.7.0 and later.
       
       The following new i5/OS options are available in ibm_db2 version 1.5.1
       and later.
       
        
         - i5_lib
- 
          
           A character value that indicates the default library that will be
           used for resolving unqualified file references. This is not valid
           if the connection is using system naming mode.
           
- i5_naming
- 
          
           DB2_I5_NAMING_ONvalue turns on DB2 UDB CLI iSeries
           system naming mode. Files are qualified using the slash (/) delimiter.
           Unqualified files are resolved using the library list for the job.
 
           DB2_I5_NAMING_OFFvalue turns off DB2 UDB CLI default
           naming mode, which is SQL naming. Files are qualified using the period (.)
           delimiter. Unqualified files are resolved using either the default library
           or the current user ID.
 
- i5_commit
- 
          
           The i5_commitattribute should be set before the
           db2_connect(). If the value is changed after the
           connection has been established, and the connection is to a remote data
           source, the change does not take effect until the next successful
           db2_connect() for the connection handle.
 注意: 
             
             The php.ini setting ibm_db2.i5_allow_commit==0
             orDB2_I5_TXN_NO_COMMITis the default, but may be
             overridden with thei5_commitoption.
 
 
           DB2_I5_TXN_NO_COMMIT- Commitment control is not used.
 
           DB2_I5_TXN_READ_UNCOMMITTED- Dirty reads, nonrepeatable
           reads, and phantoms are possible.
 
           DB2_I5_TXN_READ_COMMITTED- Dirty reads are not possible.
           Nonrepeatable reads, and phantoms are possible.
 
           DB2_I5_TXN_REPEATABLE_READ- Dirty reads and nonrepeatable
           reads are not possible. Phantoms are possible.
 
           DB2_I5_TXN_SERIALIZABLE- Transactions are serializable.
           Dirty reads, non-repeatable reads, and phantoms are not possible
 
- i5_query_optimize
- 
          
            DB2_FIRST_IOAll queries are optimized with the goal of
            returning the first page of output as fast as possible. This goal works well
            when the output is controlled by a user who is most likely to cancel the query
            after viewing the first page of output data. Queries coded with an
            OPTIMIZE FOR nnn ROWS clause honor the goal specified by the clause.
 
           DB2_ALL_IOAll queries are optimized with the goal of running
           the entire query to completion in the shortest amount of elapsed time. This is a
           good option when the output of a query is being written to a file or report, or
           the interface is queuing the output data. Queries coded with an OPTIMIZE FOR nnn
           ROWS clause honor the goal specified by the clause. This is the default.
 
- i5_dbcs_alloc
- 
          
           DB2_I5_DBCS_ALLOC_ONvalue turns on DB2 6X allocation scheme
           for DBCS translation column size growth.
 
           DB2_I5_DBCS_ALLOC_OFFvalue turns off DB2 6X allocation scheme
           for DBCS translation column size growth.
 
           Note: php.ini setting ibm_db2.i5_dbcs_alloc==0 orDB2_I5_DBCS_ALLOC_OFFis the default, but may be overridden
           with thei5_dbcs_allocoption.
 
- i5_date_fmt
- 
          
           DB2_I5_FMT_ISO- The International Organization for Standardization
           (ISO) date format yyyy-mm-dd is used. This is the default.
 
           DB2_I5_FMT_USA- The United States date format mm/dd/yyyy is used.
 
           DB2_I5_FMT_EUR- The European date format dd.mm.yyyy is used.
 
           DB2_I5_FMT_JIS- The Japanese Industrial Standard date format
           yyyy-mm-dd is used.
 
           DB2_I5_FMT_MDY- The date format mm/dd/yyyy is used.
 
           DB2_I5_FMT_DMY- The date format dd/mm/yyyy is used.
 
           DB2_I5_FMT_YMD- The date format yy/mm/dd is used.
 
           DB2_I5_FMT_JUL- The Julian date format yy/ddd is used.
 
           DB2_I5_FMT_JOB- The job default is used.
 
- i5_date_sep
- 
          
           DB2_I5_SEP_SLASH- A slash ( / ) is used as the date separator.
           This is the default.
 
           DB2_I5_SEP_DASH- A dash ( - ) is used as the date separator.
 
           DB2_I5_SEP_PERIOD- A period ( . ) is used as the date
           separator.
 
           DB2_I5_SEP_COMMA- A comma ( , ) is used as the date separator.
 
           DB2_I5_SEP_BLANK- A blank is used as the date separator.
 
           DB2_I5_SEP_JOB- The job default is used
 
- i5_time_fmt
- 
          
           DB2_I5_FMT_ISO- The International Organization for
           Standardization (ISO) time format hh.mm.ss is used. This is the default.
 
           DB2_I5_FMT_USA- The United States time format
           hh:mmxx is used, where xx is AM or PM.
 
           DB2_I5_FMT_EUR- The European time format hh.mm.ss
           is used.
 
           DB2_I5_FMT_JIS- The Japanese Industrial Standard
           time format hh:mm:ss is used.
 
           DB2_I5_FMT_HMS- The hh:mm:ss format is used.
 
- i5_time_sep
- 
          
           DB2_I5_SEP_COLON- A colon ( : ) is used as the time
           separator. This is the default.
 
           DB2_I5_SEP_PERIOD- A period ( . ) is used as the time
           separator.
 
           DB2_I5_SEP_COMMA- A comma ( , ) is used as the time
           separator.
 
           DB2_I5_SEP_BLANK- A blank is used as the time separator.
 
           DB2_I5_SEP_JOB- The job default is used.
 
- i5_decimal_sep
- 
          
           DB2_I5_SEP_PERIOD- A period ( . ) is used as
           the decimal separator. This is the default.
 
           DB2_I5_SEP_COMMA- A comma ( , ) is used as the
           decimal separator.
 
           DB2_I5_SEP_JOB- The job default is used.
 
       The following new i5/OS option is available in ibm_db2 version 1.8.0
       and later.