Originally posted by: denzer

Working in 8.2.0.4 and am looking for an adapter timeout setting for a DB call. We use DB2 and I need the WTX map to force a fail if Get function when the DB Adapter call doesn't respond in a set number of seconds. I can't find anything in the DB or general adapter documentation that there is a option or setting to set for this. Does anyone know if this is even possible?
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

is there a specific reason that you are trying fail the map if you get a timeout. Typically database connection parameters are set/contolled in the Resource management section of the dtx.ini file?
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: denzer

Yes, database connection settings are handled in the dtx.ini file but not individual DB calls. I'm looking to be able to control the wait time of the application on a specific query/adapter call. And even if that was in the dtx.ini, I'd prefer not to have a global setting but to be able to determine it on an individual query basis. I would be happy with either way at this point but I don't believe it is possible. I just want to be sure; I'd hate to think I was just missing being able to locate or find it.

Please, somebody prove me wrong.
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: TarunB

There doesn't appear to be an option in TX for this, apart from the ini file.

If you were using Oracle I would recommend NOWAIT. Prior to 11g the SQL call dropped out immediately following a lock situation (for Update). In 11g it allows specification of a time period before dropping out.

In DB2 you can use the LOCK TIMEOUT functionality but this might not be specific enough for your needs. Though you could be cheeky and SET CURRENT LOCK TIMEOUT just before your query execution and then SET it back after :-)

If you really need to control it at a map rule/query level, you could design something along the lines of:
1) Have locktimeout set to n seconds, or just work with whatever it is set at if you can.
2) Execute map/query.
3) Check return code.
4) If successful, end map.
5) If timed out, call query again.
6) Repeat 2 - 5 until you reach your required timeout level.
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender