Commit Work only for ONE Table in LUW

former_member218191 — Fri, 06 Dec 2013 16:25:42 GMT

Hi Colleagues,

I have an application that runs in the sidepanel (mainly for additional information on top of what the main applications provides) . I Want to update my statistics (how often was I called , something executed and so on) -> problem: If I do so the commit comes very late -> other users / processes wait for the LOCK to be gone (after the modify TABLE).

I cannot commit work right after the modify, because I do not want to commit data from the application that called me (in the sidepanel) .

So my first shot was

MODIFY /bcv/d_sstat connection (lc_db_conn) FROM ls_statistic.

COMMIT CONNECTION (lc_db_conn).

BUT: the connection had to be maintained in DBCON - > so I cannot deliver that because every system has own DB connections.

Second Shot.

calling a function Module starting new TASK

but that seems to me to much of an "overhead" just for that

Is there a quick and clean way to achieve that ?

Thanks Marcus

Re: Commit Work only for ONE Table in LUW

Former Member — Fri, 06 Dec 2013 16:48:18 GMT

Do the modify in a remote call and commit there. Honestly the overhead is pretty small.

Neal

Re: Commit Work only for ONE Table in LUW

former_member218191 — Fri, 06 Dec 2013 16:51:09 GMT

Hi Neal, that is what I wrote down under "Second Shot" isnt it ?

thanks Marcus

topic Re: Commit Work only for ONE Table in LUW in Application Development and Automation Discussions

Commit Work only for ONE Table in LUW

Re: Commit Work only for ONE Table in LUW

Re: Commit Work only for ONE Table in LUW