Chris
2017-09-07 14:12:20 UTC
I have a long-running AL that includes a connector to a z/OS instance of DB2. One of the tables I'm connecting to is refreshed in the wee hours of the morning, so it disappears for a short time. Because of the time it takes the AL to run, I can't simply schedule it to run during a time period that avoids the temporary unavailability of the table.
When the table goes away, the AL is failing with:
com.ibm.db2.jcc.c.SqlException: DB2 SQL error: SQLCODE: -904, SQLSTATE: 57011, SQLERRMC: 00C90086;00000200;DDVSEC2D.GDVSEC59
I already tried selecting options on the "Connection Errors" tab to no avail. I selected to Retry on Initial Connection Failure, Auto Reconnect on Connection Loss. And added to retry up to 30 times with 10 seconds between each retry. These options aren't even being exercise--he script is humming along, and then it fails immediately--in a way that makes me believe the options on the Connection Errors tab aren't even being considered.
Can anyone offer any coaching that could help? Do I have to do something special to recognize this particular error, perhaps?
Cheers,
Chris
When the table goes away, the AL is failing with:
com.ibm.db2.jcc.c.SqlException: DB2 SQL error: SQLCODE: -904, SQLSTATE: 57011, SQLERRMC: 00C90086;00000200;DDVSEC2D.GDVSEC59
I already tried selecting options on the "Connection Errors" tab to no avail. I selected to Retry on Initial Connection Failure, Auto Reconnect on Connection Loss. And added to retry up to 30 times with 10 seconds between each retry. These options aren't even being exercise--he script is humming along, and then it fails immediately--in a way that makes me believe the options on the Connection Errors tab aren't even being considered.
Can anyone offer any coaching that could help? Do I have to do something special to recognize this particular error, perhaps?
Cheers,
Chris