Is there a way to have each portal tab start back-end PGMs with different activation groups?
In this way every tab could handle system record locking to perform protected updates on the business-logic database.
In the actual situation we can't use iSeries record locking mechanism to protect multi-step updates in concurrency situations.
Thanks
In this way every tab could handle system record locking to perform protected updates on the business-logic database.
In the actual situation we can't use iSeries record locking mechanism to protect multi-step updates in concurrency situations.
Thanks
Comment