I have a DS job upserting into a DB2 table. When the job aborts the table is locked by DS. Any idea how I could solve it WITHIN DS and WITHOUT having the dba forcing the connection?
well this is a good idea but this has a performance impact on every run.
Any additional ideas to kind of reset it via DataStage which I could do only when a error had happened (hopefully rarely)
ray.wurlod wrote:If you're running the job from a sequence, use "reset if required, then run".
well I tried to see if a job reset can release the table lock after the job was aborted but it did not work.
I think this would be the same from within a sequence, wouldn't it?
I assumed you'd released the lock from within the database. DataStage doesn't have any way natively to do this, but you could issue the relevant DDL statement in a Before SQL command of a stage in a job that does nothing else.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.