If the Gateway wants to use the value of either of these gateway parameters and that value is not specified, the Gateway uses the name specified for the PLAN gateway parameter.
The Gateway uses the browse flag passed in the first message of a transaction to determine which plan to use. If the browse flag is on, the Gateway uses the browse plan, otherwise it uses the update plan. For example, if you browse a DB2 table from the table browser, the message sent is set to browse mode and the Gateway uses the browse plan. If you then select a row to invoke the single occurrence editor, another Gateway is assigned, that transaction does not have the browse flag set, and that Gateway uses the update plan.
Specifying a SCOPE of other than TRANSACTION when specifying separate browse and update plans generates an error in the Gateway start up. Only a SCOPE of TRANSACTION closes the plan at the end of a transaction. A scope of SESSION or time does not close the plan at transaction end and the next transaction inherits the previous transaction’s plan.