Versions Compared

Old Version 1

changes.mady.by.user Stonebranch

Saved on

compared with

New Version Current

changes.mady.by.user Stonebranch

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Panel
Table of Contents

...

Note
titleNote

Users can alter only the Max number of list entries and Max number of data elements settings.


IBM provides a CFSIZER web tool (Structure type OEM List ) which can be used to calculate the structure size. Given the input above, this tool returned the INITSIZE and SIZE values of 17M (at Coupling Facility Control Code Level 25). Please note that the sizes calculated by CFSIZER can vary (sometimes greatly) depending on the current CF level.

The structure name can be chosen by users and must be coded on the CF_STRUCT_NAME configuration option.

UAG uses this structure to communicate job tracking information from the Secondary agents to the Primary agent. List entries indicate events such as job start, step end and job end. List entries remain on the list until the primary agent has resources to process them. When the list structure is full, the secondary agents will wait until sufficient space is available before writing more tracking information. The required size of the structure is therefore dependent on the number of jobs being tracked, the number of job steps in those jobs and the resources available to the Primary agent to process the data.

...

NameDescription

jsc_dataset

All Primary and Secondary agents that belong to the same group must use the same UNVJSC VSAM cluster.

This cluster must be allocated on shared DASD that is available to all members in the Sysplex.

Agents that are not part of the Sysplex group must use a different VSAM cluster.

cf_struct_name

Name of the Coupling Facility structure which will be used to store the XCF Message Queue.

All Primary and Secondary agents that belong to the same group must use the same structure. The structure should not be shared between agents that are not part of the same Sysplex group.

automatic_failover

If the value of the sysplex_role parameter in UBRCFG00 is primary or secondary, this parameter can be used to control automatic failover.

Automatic failover allows a Secondary agent to become the Primary agent when the original Primary agent ends.

Valid values:

  • never
    Automatic failover will not  occur. Manual failover is still available.
  • always_primary
    For agents configured as Primary agents only. This agent should always be Primary. If another Primary agent is active when this agent starts, that agent will become a Secondary agent. If this agent cannot be a Primary  agent, it will shut down.
  • primary_secondary
    For agents configured as Primary agents only. This agent will try to start as a Primary agent. If another Primary agent is already active, this agent will become a Secondary agent. It becomes first in the ranking to become Primary during failover.
  • secondary_primary[n]
    For agents configured as Secondary agents only: This agent will start as a Secondary agent. When the Primary agent ends, this agent is eligible to become the Primary agent.
    • An optional integer [n] can be appended to this value. The integer controls the ranking of multiple Secondary agents during failover. A lower number means a higher priority in the failover ranking.
    • When multiple agents have the same ranking, the agent that started earliest will be considered to have a higher ranking.
    • Default for [n] is 1. The range is 1-32.

Default is never.

(Also see the AUTOMATIC_FAILOVER UAG configuration option.)

...

When issued against a Secondary agent

This command behaves like the z/OS STOP command (P <ubroker>).

When issued against a Primary agentThis command shuts down the Broker (and agent) while controlling the Sysplex failover behaviour:
When issued without the FAILOVER or NOFAILOVER parameter

Failover will behave as configured by the automatic_failover parameter in UAGCFG00.

When FAILOVER Is specified

An available Secondary agent will take over as Primary, regardless of how failover is configured.

When the optional <sysname> is specified, the agent running on the designated z/OS system will take over as Primary agent regardless of how fail over is configured.

When NOFAILOVER Is specifiedNo Secondary agent will take over as Primary, regardless of how failover is configured.

...