6. z/OS Parallel Sysplex Multiple systems coupled together by hardware and software services that can be viewed as a single entity. Improves: Availability Systems Management Growth 12 1 2 3 4 5 6 7 8 9 10 11 Coupling Technology Shared data Sysplex Timer ESCON/FICON 9672 zSeries
7. S/390 Sysplex Components/Terminology Sysplex A set of 1-32 z/OS systems coupled together using hardware and software elements. XCF Cross-system Coupling Facility-provides the z/OS communications services within a Sysplex. Multisystem Application An authorized application that has functions distributed across more than one z/OS system. CTC Channel to Channel connection-direct connection between two z/OS systems (ESCON CTC, 3088). Sysplex Couple Data Set A data set shared by all XCF components in a sysplex. Contains XCF-related data for the sysplex. Sysplex Timer IBM 9037 Sysplex Timer-external clock used to synchronize the TOD clocks of the systems. Member A specific function of a multisystem application that is defined to XCF and assigned to a group. Group A collection of related members. Serialization The function provided by GRS that is used to serialize resources used by XCF and other users.
8. S/390 Parallel Sysplex Components/Terminology Parallel Sysplex 2 or more z/OS images in a Sysplex using the coupling facility to share data (up to 32) XES Cross-system Extended Services-provides the z/OS communication services to the coupling facility Coupling Facility Hardware element that provides high-speed caching, list processing, and locking functions Coupling Facility Link/Channel High bandwidth fiber optic link that provides high speed connectivity required for data sharing between the CF and attached CPCs Structures Dynamically partitioned areas of storage within a coupling facility manipulated by z/OS/ESA system services Data Sharing The ability of concurrent subsystem programs to directly access and change data with integrity. Data Sharing Group Collection of two or more subsystems that access and share data in the coupling facility
9.
10.
11.
12. Sysplex Modes X C F A P P L I C A T I O N X C F A P P L I C A T I O N XCF Local XCF Monoplex X C F CTCs Couple Data sets Timer G R S A P P L I C A T I O N X C F G R S A P P L I C A T I O N XCF Multisystem Other z/OS Work Other z/OS Work Other z/OS Work Other z/OS Work Couple Data sets
13. XCF-Multisystem Sysplex Configurations X C F X C F G R S G R S A P P L A P P L Multiple Physical Processors X C F X C F G R S G R S A P P L A P P L Multiple LPARs on a Single Processor X C F X C F G R S G R S A P P L A P P L Multiple VM Guests * * * Note: Sysplex Timer and CTC considerations Processor 1 Processor 2 z/OS 1 z/OS 1 z/OS 2 z/OS 2
14.
15. XCF CTC Signalling Requirements Outbound Inbound Inbound Outbound System A System B Connecting Link At least one connecting link must be defined between each system in the Sysplex - A connecting link consists of a pair of inbound-outbound signalling paths between systems - Signalling paths are uni-directional - Recommended minimum is 4 signalling paths between each system (2 inbound and 2 outbound) XCF Logical connections:
16. XCF CTC Signalling Requirements . . Outbound Inbound Inbound Outbound Connecting Link XCF Logical connections: ESCON CTC Physical connections 600 100 601 101 SYS1 SYS2 X C F X C F PATHOUT (600) PATHIN (601) PATHIN (100) PATHOUT (101) SYS1 SYS2 ctc cnc System 1 System 2 CHPID 03 CHPID 22 System 1 I/O Definition System 1 System 2 CHPID PATH=((03)),TYPE=CTC CNTLUNIT CUNUMBR=600,PATH=((03)), UNITADD=(00,2)),UNIT=SCTC IODEVICE ADDRESS=(600,2),CUNUMBR=(600), UNIT=SCTC System 2 I/O Definition CHPID PATH=(22)),TYPE=CNC CNTLUNIT CUNUMBR=100,PATH=((22)), UNITADD=(00,2)),UNIT=SCTC IODEVICE ADDRESS=(100,2),CUNUMBR=(100), UNIT=SCTC
28. IEASYSxx Member of PARMLIB PLEXCFG=ANY, GRS=&GRSPARM, GRSRNL=PS, CON=PS, CLOCK=PS, COUPLE=&COUPLE,
29. CLOCKxx Member of PARMLIB ETRMODE YES ETRZONE YES ETRDELTA 10 TIMEZONE E.08.00.00
30. GRSRNLxx Member of PARMLIB /* System EXCLusion List */ RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN) RNAME(SYS1.LOGREC) /* System INCLusion List */ RNLDEF RNL(INCL) TYPE(GENERIC) QNAME(SYSDSN) /* System CONversion List */ RNLDEF RNL(CON) TYPE(PATTERN) QNAME(*) SYSPLEX provides the capability to dynamically change the GRS Resource Name List
38. Activating CFRM Policy Make CFRM Couple Data Set available to z/OS: SETXCF COUPLE,PCOUPLE=SYS1.CFR#PLXM.CDS01,TYPE=CFRM SETXCF COUPLE,ACOUPLE=SYS1.CFR#PLXM.CDS02,TYPE=CFRM Activate CFRM Policy: SETXCF START,POLICY,POLNAME=PLXM,TYPE=CFRM Only one member of the sysplex needs to activate the policy
39. Update COUPLExx Member of PARMLIB COUPLE SYSPLEX(&SYSPLEX) PCOUPLE(SYS1.XCF#&SYSPLEX..CDS01) ACOUPLE(SYS1.XCF#&SYSPLEX..CDS02) DATA TYPE(CFRM) PCOUPLE(SYS1.CFR#&SYSPLEX..CSD01) ACOUPLE(SYS1.CFR#&SYSPLEX..CDS02) PATHOUT STRNAME(IXCSTR1) PATHIN STRNAME(IXCSTR2)
40.
41.
42. Activating WLM Policy Make WLM Couple Data Set available to z/OS: SETXCF COUPLE,PCOUPLE=SYS1.WLM#PLXM.CDS01,TYPE=WLM SETXCF COUPLE,ACOUPLE=SYS1.WLM#PLXM.CDS02,TYPE=WLM Activate WLM Service Policy: VARY WLM,POLICY=wlm_policy_name Don't forget to update COUPLExx member
43.
44. Sysplex Failure Management z/OS A VTAM NN JES2 CMC 962 Example z/OS B VTAM EN JES2 Test onlines 390 micro VTAM EN JES2 Prod Onlines 390 micro z/OS C
45. Sysplex Failure Management z/OS A VTAM NN JES2 CMC 962 Example z/OS B VTAM EN JES2 Test onlines 390 micro VTAM EN JES2 Prod Onlines 390 micro z/OS C
46. Sysplex Failure Management z/OS A VTAM NN JES2 CMC 962 Example z/OS B VTAM EN JES2 Test onlines 390 micro VTAM EN JES2 Prod Onlines 390 micro z/OS C WT 100 WT 30 WT 80
47.
48.
49. DATA TYPE(SFM) REPORT(YES) DEFINE POLICY NAME(NORMAL) CONNFAIL(YES) REPLACE(YES) SYSTEM NAME(*) WEIGHT(1) ISOLATETIME(0) SYSTEM NAME(ZMB0) WEIGHT(40) SYSTEM NAME(ZMB1) WEIGHT(40) SYSTEM NAME(ZMB3) WEIGHT(10) RECONFIG FAILSYS(SYSC) ACTSYS(SYSD) TARGETSYS(ALL) ESTORE(YES) STORE(YES) SFM Policy Control Statements Example:
50. Activating SFM Policy Make SFM Couple Data Set available to z/OS: SETXCF COUPLE,PCOUPLE=SYS1.SFM#PLXM.CDS01,TYPE=SFM SETXCF COUPLE,ACOUPLE=SYS1.SFM#PLXM.CDS02,TYPE=SFM Activate SFM Policy: SETXCF START,POLICY,POLNAME=NORMAL,TYPE=SFM Only one member of the sysplex needs to activate the policy Update COUPLExx member
53. z/OS System Logger A P P L 2 L O G G E R A P P L 1 z/OSA Log Data Set Log Data Set A P P L 2 L O G G E R A P P L 1 z/OSB List structure logstream 1 List structure logstream 2 Coupling Facility Sysplex-Wide Offload Process Offload Process
54. CICS Tran. Server for z/OS IMS/ESA 6.1 Shared Queues Operlog Logrec APPC/MVS z/OS Resource Recovery Services Websphere TVS ... Users of System Logger: LOG WTR A z/OS_A I X G L O G R LOG WTR B CF_1 LOG WTR A z/OS_B LOG WTR B I X G L O G R System Logger Users
55.
56.
57.
58.
59.
60.
61.
62.
63.
64. ARM Environment XCF XCF ARM ARM ARM Couple Data Set Started Tasks/ Batch Started Tasks/ Batch Coupling Facility SYSA SYSB z/OS z/OS
65. ARM Restart Inplace CF SYSA SYSB RTM Error Application Automatic Restart Manager EOM Resource Manager - Invoke Exits - Determine if Element is restartable - Execute appropriate Restart Method Restart on SYSA Executing on SYSA
66. ARM Restart on other Systems ARM SYSA SYSB SYSC GRP01 Appl1 Appl2 Appl3 GRP02 Appl4 Appl5 ARM Policy Couple Data Set CF GRP01 Appl1 Appl2 Appl3 GRP02 Appl4 Appl5 SYSB leaves Sysplex XCF Address Space Applications discontinue on SYSB Restart on SYSA Restart on SYSC XCF Status update missing
67. ARM Couple Data Sets Primary ARM Couple Data Set Alternate ARM Couple Data Set Couple Data Set Format Utility . . DEFINEDS SYSPLEX(PLXM) DSN(SYS1.ARM#PLXM.CDS01) VOLSER(BMCD01) DATA TYPE(ARM) ITEM NAME(POLICY) NUMBER(3) ITEM NAME(MAXELEM) NUMBER(10) ITEM NAME(TOTELEM) NUMBER(500)