Portal tabs with different activation groups?

[MasterH]

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

[richard.milone]

VVCALL needs to run in the VALENCE activation group but beyond that you can certainly use your own activation group names. I want to make sure I fully understand what you're trying to do before I give you a full answer though. Are you trying to make multiple program calls to update data and have those all work across one commitment control process?

[MasterH]

Actually we are using a workaround that works like this:

- Before opening a new tab we call a back-end that assigns an unique numeric ID (ex: 001)

- This back-end takes VVCALL.pgm and duplicates it with a new name
and a new activation group,( ex: VVCALL001.pgm )

- Javascript then creates the tab with that ID (tab_001) and forward every request in that tab to the new vvcall (VVCALL001.pgm).

Benefits: we can have N tabs opened of the SAME function, and
N different activation groups (VVCALL001,002,003...) with different locking statuses.

[richard.milone]

Nice workaround to get what you need!