The SSMGAV2 setup requirements for OPS/MVS parameter settings, auto-enabled rules, REXX programs, resource table columns, and action table entries are discussed in this section. These requirements apply to all systems that participate in the global SSMplex.
To set up one system, follow Steps 1-8. To replicate these changes to external systems, follow Step 9.
Follow these steps:
SSMGAV2 requires the CA CCS Common Variable Service component (CAVARSRV) to run. SSMGAV2 uses the OPSVASRV() OPS/REXX function to create and maintain SYSPLEX scope variables as a database for moveable resources.
You activate the SSM global event facility, which SSMGAV2 uses to keep the SYSPLEX scope variables in sync with the SSM table data. If you already use the SSM global event facility, then you can skip this step.
To activate the global event facility, specify the following parameters:
SSMGLOBALEXITS=YES SSMGLOBALEXITTBL=RDF table name
Suggested RDF table name value (Default): SSMV2_GBLEXIT_TBL
The specified RDF table name is the name of the global events action table. SSM automatically creates it when parameter SSMGLOBALEXITS is set to YES. For information on manually creating the table before setting parameter SSMGLOBALEXITS, see the Using System State Manager chapter.
SSMGAV2 uses the SSM global event facility that you activated in Step 1 to maintain the status of moveable resources in CA OPS/MVS SYSPLEX variables. In this step, you update the SSM global events action table that the SSMGLOBALEXITTBL parameter specified.
The ADD, BEGIN, DELETE, and UPDATE global events in the global events action table must have actions that invoke the SGUPPLVA request rule. Use the following type of text for the action text for each event name. If the global event facility is already in use, then add the action text to the end of the existing action text separated by a semicolon.
ADD … RULE("SGUPPLVA &SSM!PROCESS &SSM!RESNAME")
BEGIN … RULE("SGUPPLVA &SSM!PROCESS &SSM!IPL")
DELETE … RULE("SGUPPLVA &SSM!PROCESS &SSM!RESNAME")
UPDATE … RULE("SGUPPLVA &SSM!PROCESS &SSM!RESNAME")
Note: The three periods (…) represent empty key values in the action table.
The following list describes the global events:
ADD—If the newly added resource is a moveable resource, the CA OPS/MVS SYSPLEX variables are created/updated with the current row data.
BEGIN – If AUTOHOME is set to Y for a resource, it moves to its primary system when that system is IPLed.
DELETE – Maintain the managed column list for SSMGAV2 columns.
UPDATE—If the updated resource is a moveable resource, the CA OPS/MVS SYSPLEX variables are updated with the current row data. The value of SSM#DESSYS is also evaluated to see if a move request was issued.
SSMPLEXNAME=SSMplex name
Specifies the collective name for all systems in an SSMplex. All systems in the SSMplex must be in the same SYSPLEX.
Limit: 8 character maximum
A long running server is required for the SGSYSFLR REXX code due to the wait time for the WTOR.
In addition to the normal SSM resource status rules, SSMGAV2 execution requires you to enable the following AOF rules before you initialize SSM:
This command rule is used to control or display SSMGAV2 moveable resources.
This command rule supports the following commands:
Displays all SSMGAV2 SSMplex names that are contained in the current sysplex that is connected to the system issuing this command. This command determines which SSMplex names can be used in other SSMGAV2 commands that are sent to an SSMGAV2 system for execution.
Examples:
GAV2CMD DPLEX GAPLEX
Displays the resources that are members of the specified group name for the local SSMPLEXname only. In addition, lists each resource and the group that are members.
Examples:
GAV2CMD DGROUP GAV2CMD DGROUP * GROUP4
DRES ssmplexname [tablename.resourcename|tablename.*|*.* ] [colname]
Displays status information for the resource name specified.
Examples:
GAV2CMD DRES CSSMPLEX STCTBL.* CURRENT_STATE GAV2CMD DRES * STC*.IMS* SSM#SYSLST GAV2CMD DRES CSSMPLEX *.*
Important! This command can cause voluminous output.
GAV2CMD DRES * *.*
Important! This command can cause voluminous output.
Moves the movable resource to a new system and sets the desired state to designated value.
Moves the movable resources in the specified group to a new system and sets the desired state to designated value.
Displays the syntax for the indicated command
This GLV rule is used to recover SSMGAV2 moveable resources.
This GLV rule is used to create SYSPLEX scope variables that manage cross-system prereq/subreqs.
This GLV rule is used to update SSMGAV2 moveable resources.
This GLV rule is used to POST the STATEMAN subtask when cross system PREREQs or SUBREQs are updated.
This request rule is used to create the SYSPLEX variables use by the SSMGAV2 application.
This request rule executes for the SSMGAV2 MATCH action.
This MSG rule is used to identify a system in the SSMPLEX is down and start the recovery process.
Note: This rule fires on the IXC402D sysname LAST OPERATIVE AT hh:mm:ss. message. It can be modified to fire on any event that should start the resource recovery procedure.
This request rule processes the SSM Global events.
This command rule is used by SSMGAV2 to communicate cross system using the MVS ROUTE command.
Replace the old SSMBEGIN rule with the new version that provides SSMGAV2 support.
Executes the XPREREQ and XSUBREQ process events for cross-system prereq/subreq evaluation.
The following list describes the required REXX programs:
This REXX is called by the GAV2CMD rule to process the request.
This REXX is the SSMGAV2 verify routine.
This REXX inserts a row into an SSM resource table using the SSMGAV2 SYSPLEV variables as data.
This REXX performs the move of an SSMGAV2 resource.
This REXX updates the monitored columns to include SSMGAV2 resource columns.
This REXX is called by the SGSYSFL rule to handle resource recovery when a system in the SSMPLEX is down.
This user exit is called from SGSYSFL to handle special user SSM#MOVMOD values.
This REXX creates the SYSPLEX scope variables needed for cross system PREREQ/SUBREQ processing.
This REXX creates the SYSPLEX global variables used to process cross system PREREQs and SUBREQs.
This REXX updates a row into an SSM resource table using the SSMGAV2 SYSPLEV variables as data.
This REXX processes the XPREREQ and XSUBREQ STATEMAN actions.
SSMGAV2 requires several new columns in SSM resource tables to support the functionality that SSMGA provides. Use REXX program OPSSM2CV to add the required SSMGAV2 columns to SSM resource tables by specifying a parameter of SSMGA(Y).
Strictly local resources that cannot be moved to another system do not require any column changes. Defaults for non-existent columns are supplied.
All system name values in SSMGAV2 are in the form:
sysname.subsys
Specifies the real z/OS system name.
Specifies the CA OPS/MVS subsystem name on the system (usually OPSS).
Movable resources require the following new columns:
PRIMARY_SYSTEM CHAR(14) UPPER CASE DEFAULT('*.*')
SSM#CURSYS CHAR(14) UPPER_CASE DEFAULT('*.*')
SSM#DESSYS CHAR(14) UPPER CASE DEFAULT('*.*')
SSM#MOVMOD CHAR(8) UPPER CASE DEFAULT('INACTIVE')
SSM#SYSLST VARCHAR(350) UPPER CASE
SSM#GRPLST VARCHAR(350) UPPER CASE
Optional columns:
AUTOHOME CHAR(1) UPPER_CASE DEFAULT(‘N’)
The following list describes the new columns:
Specifies the preferred system to run the resource and it is also the constant cross-system prereq specification name for resources that use the movable resource as a prerequisite. Even when the movable resource is running on an alternate system, the primary system name is still the cross-system prerequisite name: system.subsys.table.name.
Contains the current system that owns the resource.
Specifies the system name to which the resource should be moved. Changing the desired system to an alternate system name on the current system copy of the resource causes the resource to stop on the current system and move to the alternate system.
Note: The resource must be in an ACTIVE mode to be moved so it can be stopped on the current system.
Controls how the current system is selected. A value other than INACTIVE indicates that the resource is movable from the primary system to any other system specified in the SSM#SYSLST column. The alternate systems are specified as word or comma delimited list. System names are in sysname.subsys format. The sequence of alternate system names in the list is an implied priority of alternate systems for automatic selection of an alternate system.
SSMGA recognizes the following special values for SSM#MOVMOD:
– AUTO - Causes SSMGAV2 to automatically move a resource to the next available system in the system list hierarchy when a failure is detected on the owning system.
-WTOR – Causes SSMGAV2 to issue the GAV2911I MLWTO and GAV2911O WTOR which prompts users to recover a list of moveable resources.
Users can add code to the SGSYSFLU user exit to take special actions for user defined SSM#MOVMOD values.
Any other value of move mode allows movement of resources by manually changing the desired system to an alternate system.
Lists all of the available systems to which you can move the resource.
(Optional) Specifies SSM resources, such as a workload, global status, or disaster recovery eligibility, using arbitrary 1-18 character names. The ISPF monitoring tool uses the group names in SSMGAV2 to move groups of resources and in the operator command facility for query and action commands. The list of group names is word or comma delimited. SSMGAV2 monitors the resource group name list for changes.
Once the required columns have been added to the resource tables, enter the column data values.
Define cross-system resource prerequisites by updating the prereq column with the full cross-system name of the resource:
system.subsys.table.name
SSMGAV2 requires that the following actions be added to the SSM resource action tables.
ACTION_ | ACTION_ | ACTION_
PROCESS |CURRENT |MODE |ACTION_TEXT
---------------------------------------------------------------------------------
SELECT … … PROCESS("MATCH ")
MATCH DOWN MOVING SETCOL("ACTMODE,ACTIVE");RULE("SGMOVRS1 &SSM!TABLE &SSM!NAME")
XPREREQ … … RULE(SSMG2PRX &SSM!PROCESS
&SSM!PREREQ PRERES(&SSM!RESNAME)")
XSUBREQ … … RULE(SSMG2PRX &SSM!PROCESS &SSM!XRESNAME")
Each eligible system (the primary system and all alternate systems) for each movable resource must have an identical associated action table, and identical AOF rules (if not using shared AOF rule sets) for that movable resource. You must set the required SSMGAV2 parameters on each system that participates in the global SSMplex.
To replicate parameters, RDF tables, and rules:
|
Copyright © 2014 CA.
All rights reserved.
|
|