+

Search Tips   |   Advanced Search

(zos)

Tune GRS when using global transactions in z/OS

WebSphere Application Server for z/OS uses global resource serialization (GRS) to communicate information between servers in a sysplex. When there are multiple servers defined in a system or a sysplex, a request might end up on the wrong server. WebSphere Application Server for z/OS uses GRS to determine where the transaction is running.

If we are using global transactions, WebSphere Application Server for z/OS issues an enqueue for a transaction when the transaction starts and holds on to that enqueue until the transaction ends.

WebSphere Application Server for z/OS uses GRS enqueues in the following situations:

If we are not in a sysplex, you should configure GRS=NONE, or if you are in a sysplex, you should configure GRS=STAR.

This requires configuring GRS to use the coupling facility. All of the WAS enqueues are issued with RNL=NO, which prevents misconfiguring the GRSRNLxx with inappropriate values. See the GRS documentation for details on setting this up.

Avoid trouble: For a GRS ring to attach one or more monoplexes to a sysplex environment, the cell name of any servers running in any of the monoplexes must be unique within the entire GRS environment. This requirement means that the cell name of a server running in any of the monoplexes:

If we have servers with duplicate cell names within the GRS environment, WebSphere Application Server for z/OS cannot differentiate between the sysplex cell and the monoplex cell, and treats both servers as part of the same cell. This inaccurate cell association typically causes unpredictable processing results.gotcha


Related

  • Tune parameter hot list