The Lock Required on Entry option allows locking of an occurrence in an import view at entry to the action block. Locking an occurrence prevents other transactions from changing the view. When you add an entity type to a view, this characteristic becomes available for selection only if the view supports entity actions.
Those views in which occurrences are to be locked are labeled locked in the Action Diagram view list. Those views in which occurrences are not locked are labeled unlocked. The default value is unlocked.
The Locked parameter is strictly a means of communication at code generation time. The generator checks the view matching on USE statements to determine the intent of called action blocks regarding the views that are being passed. Use the Locked parameter on the receiving persistent view if any entity actions are planned.
Downstream Effects: When an action block or procedure reads an entity action view that is matched to a view in a called action block marked 'locked,' this signals code generation to create a cursor with locking. The implication is that the called action block intends to update the database using this matched entity action view.
|
Copyright © 2014 CA.
All rights reserved.
|
|