PM39632: Adding parameter(s) to a Data Source Explorer 'DB2 for i5/OS' connection URL, does not persist.

Rational Application Developer for WebSphere Software 8.5
Rational Software Architect Interim Fix 1 for 8.0.4.2
Rational Software Architect for WebSphere Software Interim Fix 1 for 8.0.4.2

APAR status

• Closed as program error.

Error description

• Abstract:
  
  Data Source Explorer ? Database Connection (an existing
  connection) ? Properties ? Driver Properties
  ?  Drivers: .... (field)  ? 'triangle icon' (Edit Driver
  definitions) ? Properties [Tab] allows you to edit any
  [property,value] pair such as Connection URL.
  However they are not reflected back to the 'Properties' wizard
  page (as in not persisted).
  
  Problem:
  
  Any new parameters added to a Data Source Explorer 'DB2 for
  i5/OS' connection are not persisted.
  
  
  Example:
  
  Connection url: jdbc:as400:{host};prompt=falso;date format=iso
  Database name : {host}
  Driver Class  : com.ibm.as400.access.AS400JDBCDriver
  
  Sampling a DATE1 field returns NULL even though the DATE1 is of
  type: date not null with default, and has a default value of
  '1900-01-01'
  
  This happens because editing the Connection URL in the 'Edit
  Driver Definition' wizard to add the 'date
  format=iso' property does not persist it and it is not added to
  the actual connection URL that the system is using to connect to
  the database.
  
  Answer and 'possible' Fix(s):
  
  This is working as designed.
  The Properties are not editable.
  Consequently, they should be greyed out.
  However this is not the primary focus of this APAR
  
  Primary focus is that
  it should be possible to change/edit existing database  Driver
  properties at the workspace
  Preferences  ? Data Management ? Driver definitions
  and the change would be available in any 'New...'  connection
  created in the Data Source Explorer for this workspace
  
  Also, Using  [Add] a new driver in the Data Management ? Driver
  definitions workspace preferences , using a specific vendor
  template (other then Other Driver...),  does not allow editing
  properties. This should also be similarly fixed
  
  Workaround:
  
  It is not a problem if you specify to use 'Other driver' and
  specify all the info such as the JDBC driver JAR file, class,
  etc with the same values as the Toolbox driver.
  
  Workaround Example for Other Driver, DB2 for i5/OS,V5R3:
  
  The 'Other Driver' is setup under
  Window ? Preferences ? Data Management ? Driver Definitions
  , using the 'Add' button
  In the 'New Driver Definition' wizard
  
  1. In 'Specify a driver Template and Definition' page
  (a) 'Name/Type' Tab
  - Under Available driver templates:
  select: Other Driver, DB2 for i5/OS,V5R3
  - In 'Driver Name' enter a name of your choice
  
  (b) 'JAR List' Tab ,
  , use 'Add JAR/zip' button
  
  - In 'Select a File' page navigate to a jt400.jar
  For example in RAD v8.0.2, you can use
  {RAD Install
  dir}\SDP70Shared\plugins\com.ibm.datatools.db2.iseries_3.1.100.v
  20100715_2051\driver\jt400.jar
  
  (c) 'Properties' Tab
  specify the Properties:
  Connection url: jdbc:as400:{host};prompt=falso;date format=iso
  Database name : {host}
  Driver Class  : com.ibm.as400.access.AS400JDBCDriver
  
  2. ALTERNATIVELY for DB2 platforms ,  Edit an existing:
  
  Other Driver Default   |   DB2 for { i5/OS | z/OS | Linux,Unix,
  and Windows}     |     v{m}r{n}
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Parameters added to the Data Source Explorer for IBM
  database vendors like DB2 LUW, DB2 i5/OS, DB2 Z/OS and
  Informix of some drivers connection URL are not persisted.
  

Problem conclusion

• This issue is fixed in Rational Application Developer
  V8.0.4.1.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  RATL APP DEV WI

• Fixed component ID

  5724J1901

Applicable component levels

• R800 PSN

     UP