Parallel Sysplex Implement2

7,847 views

Published on

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
7,847
On SlideShare
0
From Embeds
0
Number of Embeds
34
Actions
Shares
0
Downloads
315
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Parallel Sysplex Implement2

  1. 1. Parallel Sysplex Implementation Parallel Sysplex Center Poughkeepsie, NY USA
  2. 2. Trademarks <ul><li>The following terms used in this presentation are trademarks of the IBM Corporation </li></ul><ul><ul><li>ACF/VTAM </li></ul></ul><ul><ul><li>CICS/ESA </li></ul></ul><ul><ul><li>DB2 </li></ul></ul><ul><ul><li>DFSMS/z/OS </li></ul></ul><ul><ul><li>ESA/390 </li></ul></ul><ul><ul><li>ESCON </li></ul></ul><ul><ul><li>ES/9000 </li></ul></ul><ul><ul><li>IBM </li></ul></ul><ul><ul><li>z/OS/ESA SP </li></ul></ul><ul><ul><li>PR/SM </li></ul></ul><ul><ul><li>PS/2 </li></ul></ul><ul><ul><li>RACF </li></ul></ul><ul><ul><li>S/390 </li></ul></ul><ul><ul><li>SYSPLEX TIMER </li></ul></ul><ul><ul><li>VM/ESA </li></ul></ul><ul><ul><li>VTAM </li></ul></ul>
  3. 3. <ul><li>Overview </li></ul><ul><ul><li>Pre-Sysplex Multisystem Applications </li></ul></ul><ul><li>z/OS Parallel Sysplex </li></ul><ul><ul><li>Components/Terminolgy </li></ul></ul><ul><ul><li>Multisystem Sysplex Requirements </li></ul></ul><ul><ul><li>IBM 9037 Sysplex Timer </li></ul></ul><ul><ul><li>XCF Signalling Requirements </li></ul></ul><ul><ul><li>XCF Sysplex Couple Data Sets </li></ul></ul><ul><ul><li>GRS in a Sysplex </li></ul></ul><ul><ul><li>Parallel Sysplex Resource Managers </li></ul></ul><ul><ul><li>Policies </li></ul></ul>Agenda
  4. 4. <ul><li>Parallel Sysplex Implementation Steps </li></ul><ul><li>Summary </li></ul><ul><li>Parallel Sysplex Extensions </li></ul><ul><ul><li>z/OS Logger </li></ul></ul><ul><ul><li>Automatic Restart Manager (ARM) </li></ul></ul><ul><ul><li>Sysplex Failure Manager (SFM) </li></ul></ul>Agenda (cont.)
  5. 5. Pre-Sysplex Multisystem Applications CICS IMS JES2 VTAM GRS JES3 CONSOLES JES2 IMS CICS VTAM GRS JES3 CONSOLES CTC CTC CTC MCS MCS JES3 MVS MCS MVS
  6. 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. 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. 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. 9. Role of the CF LOCKS DATA BUFFERS DATABASE MANAGER DATA BUFFERS DATABASE MANAGER z/OS Sysplex Services Coupling Technology REQUESTS REQUESTS z/OS S/390 z/OS S/390 <ul><li>Locks </li></ul><ul><li>Lists </li></ul><ul><li>Caches </li></ul>LOCKS <ul><li>Multi-System </li></ul><ul><ul><li>Serialization </li></ul></ul><ul><ul><li>Changed Data </li></ul></ul>
  10. 10. Multisystem Parallel Sysplex Requirements <ul><li>Requirements for all systems in an z/OS Sysplex: </li></ul><ul><ul><li>Be connected to a common time source </li></ul></ul><ul><ul><li>Use the same Couple Data Sets </li></ul></ul><ul><ul><li>Be in the same GRS configuration </li></ul></ul><ul><ul><li>Have full connectivity to every other system in the Sysplex </li></ul></ul><ul><ul><li>Have unique system names within the Sysplex </li></ul></ul><ul><ul><li>Specify the same Sysplex name </li></ul></ul><ul><ul><li>Have connectivity to all CFs </li></ul></ul>
  11. 11. IBM 9037 Sysplex Timer S0000 Main Menu Time Help Ports Profile Log Maint 01/09/90 09:17:23 UTC Status changed. View log for details. F1=Help 9037 Sysplex Timer Unit (TOD) Clock Management using ETR Synchronization Mode <ul><li>TOD values kept in synchronization with the Sysplex Timer </li></ul><ul><li>No operator intervention required to set TOD clocks </li></ul><ul><li>Expanded availability configuration is strongly recommended </li></ul>
  12. 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. 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. 14. <ul><li>Full Connectivity to all systems is required </li></ul><ul><ul><li>Redundant configurations are recommended </li></ul></ul><ul><li>Potential configurations include: </li></ul><ul><ul><li>ESCON Channels operating in CTC mode ( Point-to-Point ) </li></ul></ul><ul><ul><ul><li>Channels supporting CTC communications must be paired; one operating in CTC ( Type=CTC ) mode and the other operating in native mode ( Type=CNC ) </li></ul></ul></ul><ul><ul><li>ESCON Channels with ESCON Directors ( ESCD ) </li></ul></ul><ul><ul><ul><li>Reduces the number of CTCs that must be used </li></ul></ul></ul><ul><ul><ul><li>Allows the native ESCON channels to be used for attaching other ESCON devices </li></ul></ul></ul><ul><ul><li>PR/SM LPARs with ESCON Multiple Image Facility </li></ul></ul><ul><ul><ul><li>Using shared channels further reduces channel requirements </li></ul></ul></ul><ul><ul><li>Signalling structures </li></ul></ul>z/OS Sysplex Connectivity
  15. 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. 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
  17. 17. <ul><li>XES signalling provides the ability to establish XCF signalling connectivity through the coupling facility </li></ul><ul><ul><li>In addition to, or instead of, the existing signalling capability using CTC links </li></ul></ul><ul><li>XES automatically configures paths to all systems using a common CF list structure </li></ul><ul><ul><li>Defining a coupling facility list structure as an outbound definition for XCF will cause an XCF signalling path to be established with every other system that has the structure defined as an inbound path </li></ul></ul><ul><ul><li>A coupling facility list structure can be defined and be used for both outbound and inbound XCF signalling paths </li></ul></ul>XES Signalling Structures
  18. 18. <ul><li>Installation </li></ul><ul><ul><li>Unidirectional, point-to-point; Minimum CTC paths to provide full connectivity for 8 system Sysplex is 56 (8*(8-1)); 112 for redundancy </li></ul></ul><ul><ul><li>Bidirectional, one-to-many; one coupling facility list structure can support more than an 8 system Sysplex; 2 for redundancy </li></ul></ul><ul><li>Administration </li></ul><ul><ul><li>PARMLIB, I/O Definition, Shared COUPLExx member not practical because of CTC addresses </li></ul></ul><ul><ul><li>PARMLIB, Administrative policy, shared COUPLExx member possible if all systems share the same list structure(s) and all other XCF parameters are the same </li></ul></ul><ul><li>Recovery </li></ul><ul><ul><li>Manual </li></ul></ul><ul><ul><li>XES and Coupling Facility initiated </li></ul></ul>XCF CTC XES Signalling XES Signalling XES Signalling XCF CTC XCF CTC XCF CTC Signalling versus XES Signalling
  19. 19. COUPLE SYSPLEX (PLXM) PCOUPLE (SYS1.XCF#PLXM.CDS01) ACOUPLE (SYS1.XCF#PLXM.CDS02) PATHIN STRNAME(IXCSTR1) PATHOUT STRNAME(IXCSTR2) Signalling Definitions Coupling Facility CTC COUPLE SYSPLEX (PLXM) PCOUPLE (SYS1.XCF#PLXM.CDS01) ACOUPLE (SYS1.XCF#PLXM.CDS02) PATHIN DEVICE(E40,E41) PATHIN DEVICE(890,891) PATHOUT DEVICE(100,101) PATHOUT DEVICE(200,201)
  20. 20. XCF Sysplex Couple Data Set <ul><li>Required for XCF-Monoplex or XCF-Multisystem Sysplex modes </li></ul><ul><li>An alternate couple data set may be specified </li></ul><ul><li>Couple data set(s) must be shared by all systems in the Sysplex </li></ul><ul><li>Some information kept in the couple data set includes: </li></ul><ul><ul><li>Names of the systems in the Sysplex </li></ul></ul><ul><ul><li>Status of the systems in the Sysplex </li></ul></ul><ul><ul><li>A system status field that is periodically updated by each system to indicate its &quot;health&quot; </li></ul></ul><ul><ul><li>Names of groups and members </li></ul></ul><ul><ul><li>Member status for members using permanent status recording </li></ul></ul><ul><li>All systems in the Sysplex will go in wait state, if couple data set(s) are not usable </li></ul><ul><li>Defined in PARMLIB; May be added or removed using SETXCF </li></ul>Shared data repository for the systems in a Sysplex
  21. 21. XCF Sysplex Couple Data Set . . . <ul><li>Avoid placing Couple Data set on volume with high use data sets </li></ul><ul><li>Avoid a volume that has the RESERVE macro issued against it </li></ul><ul><li>Normal I/O activity - Status Updates - 2 I/Os every 3 seconds per system in Sysplex </li></ul><ul><li>Additional I/O activity </li></ul><ul><ul><li>I/O to the Couple Data Set for every action message in Sysplex (for example, WTOR) </li></ul></ul><ul><ul><li>Modifications to the Sysplex (for example, activation of a new group) </li></ul></ul><ul><ul><li>During recovery </li></ul></ul>
  22. 22. <ul><li>GRS Multisystem (Global) serialization is required for XCF-Multisystem Sysplex mode </li></ul><ul><li>In a multisystem Sysplex GRS can use lock structure to manage GRS configuration. Benefits: </li></ul><ul><ul><li>Improved Performance </li></ul></ul><ul><li>All systems in the Sysplex must be in the same GRS configuration </li></ul>Global Resource Serialization in a Sysplex z/OS z/OS RSA RNLs RNLs CTC G R S G R S X C F X C F
  23. 23. z/OS Parallel Sysplex Resource Manager Policies <ul><li>Sysplex-wide administrative policies </li></ul><ul><ul><li>Automated, system-managed goals </li></ul></ul><ul><ul><li>Changes communicated to all systems in the sysplex </li></ul></ul><ul><ul><li>Dynamically changed using commands </li></ul></ul><ul><ul><li>IPL not required </li></ul></ul><ul><li>z/OS Coupling Facility Resource Manager (CFRM) Policy </li></ul><ul><li>z/OS Sysplex Failure Mangement (SFM) Policy </li></ul><ul><li>z/OS Workload Manager (WLM) Policy </li></ul><ul><li>z/OS Automatic Restart Manager (ARM) Policy </li></ul><ul><li>z/OS Logger Inventory </li></ul>
  24. 24. Parallel Sysplex Implementation Steps
  25. 25. Planning for a z/OS Parallel Sysplex <ul><li>Review: </li></ul><ul><ul><li>Sysplex Implementation Requirements </li></ul></ul><ul><ul><ul><li>z/OS Sysplex and S/390 Parallel Sysplex </li></ul></ul></ul><ul><ul><ul><li>Software/Hardware </li></ul></ul></ul><ul><ul><li>Network Considerations </li></ul></ul><ul><ul><li>Potential Applications </li></ul></ul><ul><ul><li>Operations Changes </li></ul></ul><ul><ul><li>Testing Requirements </li></ul></ul>
  26. 26. Customization Tasks for Parallel Sysplex <ul><li>SYS1.PARMLIB </li></ul><ul><ul><li>IEASYMxx </li></ul></ul><ul><ul><ul><li>SYSNAME, SYMDEF definitions </li></ul></ul></ul><ul><ul><li>IEASYSxx </li></ul></ul><ul><ul><ul><li>SYSNAME, GRS, GRSCNF, CLOCK, PLEXCFG, CON, COUPLE </li></ul></ul></ul><ul><ul><li>CLOCKxx </li></ul></ul><ul><ul><li>GRSCNFxx </li></ul></ul><ul><ul><li>GRSRNLxx </li></ul></ul><ul><ul><li>CONSOLxx </li></ul></ul><ul><ul><li>COUPLExx </li></ul></ul><ul><ul><ul><li>SYSPLEX name, COUPLE data sets, Signalling paths </li></ul></ul></ul><ul><li>Format Couple data sets </li></ul><ul><li>IPL with new configuration </li></ul><ul><li>Bring other systems into the SYSPLEX </li></ul>
  27. 27. IEASYMxx Member of PARMLIB SYSDEF SYSCLONE(&SYSNAME(3:2)) SYSPARM(PS) SYMDEF(&SYSR1='BMRS11') SYMDEF(&SYSR2='&SYSR1(1:5).2') SYMDEF(&GRSPARM=‘STAR’) SYMDEF(&COUPLE=‘PS’) SYSDEF HWNAME(AB02) LPARNAME(Z021) SYSNAME(ZMB0) SYMDEF(&APPN='8B') SYMDEF(&SSCPID='811') SYSDEF HWNAME(AB01) LPARNAME(Z011) SYSNAME(ZMB1) SYMDEF(&APPN='8C') SYMDEF(&SSCPID='812')
  28. 28. IEASYSxx Member of PARMLIB PLEXCFG=ANY, GRS=&GRSPARM, GRSRNL=PS, CON=PS, CLOCK=PS, COUPLE=&COUPLE,
  29. 29. CLOCKxx Member of PARMLIB ETRMODE YES ETRZONE YES ETRDELTA 10 TIMEZONE E.08.00.00
  30. 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
  31. 31. Implementing Parallel Sysplex <ul><li>Format SYSPLEX couple data sets </li></ul><ul><ul><li>Update COUPLExx for signalling paths </li></ul></ul><ul><li>Format other couple data sets </li></ul><ul><ul><li>Coupling Facility Resource Management (CFRM) </li></ul></ul><ul><ul><li>Sysplex Failure Management (SFM) </li></ul></ul><ul><ul><li>Workload Management (WLM) </li></ul></ul><ul><ul><li>Automatic Restart Management (ARM) </li></ul></ul><ul><li>Define CF structures </li></ul><ul><ul><li>XCF/XES signalling </li></ul></ul><ul><ul><li>VTAM </li></ul></ul><ul><ul><li>JES2 </li></ul></ul><ul><ul><li>RACF </li></ul></ul><ul><ul><li>IRLM </li></ul></ul><ul><ul><li>LOGGER </li></ul></ul><ul><ul><li>others...... </li></ul></ul>
  32. 32. Sysplex Couple Data Set <ul><li>Required for: </li></ul><ul><ul><li>XCF-Multisystem and XCF-Monoplex </li></ul></ul><ul><li>Must be shared by ALL systems in sysplex </li></ul><ul><li>Avoid placing on busy volumes </li></ul><ul><li>Define primary and alternate </li></ul><ul><ul><li>Alternate is optional but recommended </li></ul></ul><ul><ul><li>Defined by IXCL1DSU batch utility </li></ul></ul><ul><ul><ul><li>IXCSYSPF in SYS1.SAMPLIB </li></ul></ul></ul>Control Statement: DEFINEDS DSN(SYS1.XCF#PLXM.CDS01) VOLSER(BMCD01) SYSPLEX(PLXM) MAXSYSTEM(6) CATALOG DATA TYPE(SYSPLEX) ITEM NAME(GROUP) NUMBER(20) ITEM NAME(MEMBER) NUMBER(50)
  33. 33. COUPLE SYSPLEX (PLXM) PCOUPLE (SYS1.XCF#PLXM.CDS01) ACOUPLE (SYS1.XCF#PLXM.CDS02) PATHIN STRNAME(IXCSTR1) PATHIN DEVICE(E40,E41) PATHIN DEVICE(890,891) ... ... PATHOUT STRNAME(IXCSTR1) PATHOUT DEVICE(100,101) PATHOUT DEVICE(200,201) ... ... Signalling Definitions - COUPLExx Coupling Facility CTCs
  34. 34. Coupling Facility Resource Manager Policy <ul><li>Coupling Facility Resource Manager (CFRM) policy </li></ul><ul><ul><li>Defines Coupling Facilities (CFs) to be used </li></ul></ul><ul><ul><ul><li>Type of Coupling Facility </li></ul></ul></ul><ul><ul><ul><li>CPCID </li></ul></ul></ul><ul><ul><ul><li>Sequence Number </li></ul></ul></ul><ul><ul><ul><li>etc..... </li></ul></ul></ul><ul><ul><li>Defines structures and their placement in the CFs </li></ul></ul><ul><ul><ul><li>Preference List, Exclusion List </li></ul></ul></ul><ul><ul><li>Batch Administrative Utility </li></ul></ul>
  35. 35. Define CFRM Couple Data Set <ul><li>IXCCFRMF member in SYS1.SAMPLIB </li></ul><ul><ul><li>Execute IXCL1DSU batch utility </li></ul></ul><ul><ul><li>Alternate CFRM couple data set is HIGHLY recommended </li></ul></ul>Control Statements: DEFINEDS SYSPLEX(PLXM) DSN(SYS1.CFR#PLXM.CDS01) VOLSER(BMCD02) CATALOG DATA TYPE (CFRM) ITEM NAME(POLICY) NUMBER(6) ITEM NAME(CF) NUMBER(5) ITEM NAME(STR) NUMBER(20) ITEM NAME(CONNECT) NUMBER(32)
  36. 36. Define CFRM Policy <ul><li>IXCCFRMP member in SYS1.SAMPLIB </li></ul><ul><ul><li>Execute IXCMAIPU administrative data utility </li></ul></ul><ul><ul><ul><li>CFRM couple data set must be pre-formatted </li></ul></ul></ul><ul><ul><li>IXCMAIPU administrative data utility is used to add </li></ul></ul><ul><ul><li>update, or delete policy data </li></ul></ul><ul><ul><li>Structure sizes must be estimated </li></ul></ul><ul><ul><ul><li>CFSizer has recommendations </li></ul></ul></ul><ul><ul><li>RACF protect IXCMAIPU </li></ul></ul><ul><ul><ul><li>Resource name ‘MVSADMIN.XCF.CFRM' in FACILITY class </li></ul></ul></ul>
  37. 37. DATA TYPE(CFRM) REPORT(YES) DEFINE POLICY NAME(PLXM) REPLACE(YES) CF NAME(C033) TYPE(002064) MFG(IBM) PARTITION(3) SEQUENCE(000000019B1A) CPCID(00) CF NAME(C021) TYPE(002064) ... ... STRUCTURE NAME(IXCPATH1) SIZE(16316) PREFLIST(C033,C021) REBUILDPERCENT(1) STRUCTURE NAME(ISTGENERIC) SIZE(10000) PREFLIST(C033,C021) STRUCTURE NAME(ISTMNPS) SIZE(12288) PREFLIST(C021,C033) STRUCTURE NAME(IXCPATH2) SIZE(16316) PREFLIST(C021,C033) EXCLLIST(IXCSTR1) CFRM Policy Control Statements Example: C033 C021 IIXCPATH1 ISTGENERIC ISTMNPS IXCPATH2
  38. 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. 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. 40. z/OS Workload Manager Policy <ul><li>z/OS Workload Manager (WLM) Policy </li></ul><ul><li>Performance goals </li></ul><ul><ul><li>Not parameter driven </li></ul></ul><ul><ul><ul><li>Replaces SRM IPS & ICS </li></ul></ul></ul><ul><ul><ul><li>Business importance </li></ul></ul></ul><ul><li>ISPF Dialogs to define </li></ul>
  41. 41. Define WLM Couple Data Sets <ul><li>IWMFTCDS member in SYS1.SAMPLIB </li></ul><ul><ul><li>Execute IXCL1DSU batch utility </li></ul></ul><ul><ul><li>Alternate WLM couple data set is strongly recommended </li></ul></ul><ul><ul><li>Define resource name MVSADMIN.WLM.POLICY in the FACILITY class of RACF </li></ul></ul><ul><ul><ul><li>Use PERMIT to allow access </li></ul></ul></ul>Control Statements: DEFINEDS SYSPLEX(PLXM) DSN(SYS1.WLM#PLXM.CDS01) VOLSER(BMCD01) CATALOG DATA TYPE (WLM) ITEM NAME(POLICY) NUMBER(6) ITEM NAME(WORKLOAD) NUMBER(35) ITEM NAME(SRVCLASS) NUMBER(100)
  42. 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. 43. Sysplex Failure Management Policy <ul><li>Sysplex Failure Mangement (SFM) policy </li></ul><ul><ul><li>Automates Sysplex recovery actions: </li></ul></ul><ul><ul><ul><li>Loss of connectivity </li></ul></ul></ul><ul><ul><ul><li>System status update missing </li></ul></ul></ul><ul><ul><ul><li>Storage Reconfiguration </li></ul></ul></ul><ul><ul><li>Batch Administrative Utility </li></ul></ul>
  44. 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. 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. 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. 47. Define SFM Couple Data Set <ul><li>IXCSFMF member in SYS1.SAMPLIB </li></ul><ul><ul><li>Execute IXCL1DSU batch utility </li></ul></ul><ul><ul><li>Alternate SFM couple data set is recommended </li></ul></ul>Control Statements: DEFINEDS SYSPLEX(PLXM) DSN(SYS1.SFM#PLXM.CDS01) VOLSER(BMCD01) CATALOG DATA TYPE (SFM) ITEM NAME(POLICY) NUMBER(6) ITEM NAME(SYSTEM) NUMBER(8) ITEM NAME(RECONFIG) NUMBER(4)
  48. 48. Define Sysplex Failure Management Policy <ul><li>IXCSFMP member in SYS1.SAMPLIB </li></ul><ul><ul><li>Execute IXCMAIPU administrative data utility </li></ul></ul><ul><ul><ul><li>SFM couple data set must be pre-formatted </li></ul></ul></ul><ul><ul><li>IXCMAIPU administrative data utility is used to add </li></ul></ul><ul><ul><li>update, or delete policy data </li></ul></ul><ul><ul><li>RACF protect IXCMAIPU </li></ul></ul><ul><ul><ul><li>Resource name ‘MVSADMIN.XCF.SFM' in FACILITY class </li></ul></ul></ul>
  49. 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. 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
  51. 51. CDS Types: Sysplex Couple Data Set CFRM SFM Separate/Combined WLM Allocation: Space requirements Primary/Alternate Format: IXCL1DSU (All) ADMIN: IXCMIAPU (CFRM,SFM) ISPF Interface (WLM) Sysplex Implementation Summary Sysplex Implementation Activities IEASYSxx: PLEXCFG GRS GRSCNF GRSCNFxx GRSRNL GRSRNLxx CLOCK CLOCKxx CONSOLE CONSOLxx CNGRPxx COUPLE COUPLExx CSS Configuration OS Configuration IOCDS Security Profiles CBD.CPC.IOCDS CBD.CPC.IPLPARM IPLPARM HMC Setup Profiles SYSPLEX Name Network Name (S/390 T/R) Processor Id names (HCD) CPC Names CF Names Structures Consoles JES2 Checkpoint Signalling Paths z/OS System Names HW/SW Requirements HCD PARMLIB Planning COUPLE
  52. 52. <ul><li>Define checkpoint structure in CFRM </li></ul><ul><li>CKPTDEF Parameters </li></ul><ul><ul><li>CKPTn=(STRNAME=str_name) </li></ul></ul><ul><ul><li>MODE=DUPLEX </li></ul></ul><ul><li>Recommendations </li></ul><ul><ul><li>CKPT1 on CF, CKPT2 on DASD </li></ul></ul><ul><ul><li>VOLATILE=(ONECKPT=IGNORE,ALLCKPT=DIALOG) </li></ul></ul><ul><ul><li>Activate via Dialog </li></ul></ul>JES2 Checkpoint on CF
  53. 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. 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. 55. System Logger Recommendations <ul><li>Logstream/Structure Recommendations: </li></ul><ul><ul><li>Aim for 10-20 logstreams per structure. During recovery, each z/OS will maximize parallelism ACROSS structures, but serially within a single structure. Remember (current) overall limit of 255 structures. </li></ul></ul><ul><ul><li>Try to have at least 2 active logstreams per CF structure, connected to more than one system, to allow peer recovery in case of failure. </li></ul></ul><ul><ul><li>Try to put logstreams with similar storage requirements in same structure - storage is split evenly between all logstreams, so CF storage will be wasted if logstreams have vastly different usage patterns. </li></ul></ul><ul><ul><li>When another logstream is connected, the existing logstreams will be re-sized. This could potentially cause short term logstream-full conditions and impact exploiters. </li></ul></ul>
  56. 56. <ul><li>Logstream/Structure Recommendations: </li></ul><ul><ul><li>AVGBUFSIZE & MAXBUFSIZE are specified at structure level, so try to ensure all logstreams in a structure have similar block size characteristics. </li></ul></ul><ul><ul><li>Use a realistic number for LOGSNUM - every POTENTIAL logstream takes up some storage in the structure. </li></ul></ul><ul><ul><li>Do not oversize the logstream structures - every logstream is potentially duplexed in a data space - so very large logstreams can lead to processor storage constraint. Also, very large logstreams mean long offloads which can impact logger performance. More frequent small offloads are better than a few large ones. One offload every 5-10 minutes would be an ideal balance. </li></ul></ul>System Logger Recommendations cont...
  57. 57. <ul><li>Offload Dataset Recommendations: </li></ul><ul><ul><li>Use a CISZ of 24576 for offload datasets. Staging datasets MUST have a CISZ of 4096 or writes to them will fail. </li></ul></ul><ul><ul><li>Make the offload datasets as large as reasonable , to reduce overhead of allocating additional datasets in the middle of an offload. Bear in mind retpd and age of data in each offload dataset. </li></ul></ul><ul><ul><li>RETPD and AUTODELETE to control deletion of data from logstream and deletion of log data sets. </li></ul></ul><ul><ul><li>Ensure data sets are defined with SHROPTIONS(3,3) </li></ul></ul>System Logger Recommendations cont...
  58. 58. <ul><li>Recommendations: </li></ul><ul><ul><li>For OLTP workloads, use HIGHOFFLOAD of 80% and LOWOFFLOAD of 60% as a starting point. Check the documentation for the connector (CICS or whatever) for specific recommendations, and monitor SMF Type 88 records using IXGRPT1 provided in SAMPLIB. </li></ul></ul><ul><ul><li>Do not set HIGHOFFLOAD higher than 80%, in case spurts of activity would fill the log stream before OFFLOAD can provide additional space. </li></ul></ul><ul><ul><li>Do not set HIGHOFFLOAD so high that you rarely get offloads - log stream and offload data sets only get cleaned up when offload is invoked. </li></ul></ul><ul><ul><li>Make sure you have sufficient auxiliary storage to back the logger data spaces. </li></ul></ul><ul><ul><li>IXGRPT1 provides counts of number of offloads, number of structure full and entry full, and avg buffer size, amongst other things. See SMF manual, macro IXGSMF88 in SYS1.MACLIB, and member IXGRPT1 in SYS1.SAMPLIB for a description of all the fields. </li></ul></ul>System Logger Recommendations cont...
  59. 59. <ul><li>Offload devices should be fast enough to offload difference between HIGHOFFLOAD and LOWOFFLOAD faster than space above HIGHOFFLOAD fills up. </li></ul>System Logger Review
  60. 60. Format Logger Inventory <ul><li>Format the z/OS Logger Inventory Couple Data Set with: </li></ul><ul><ul><li>LSR – number of structures </li></ul></ul><ul><ul><li>LSTRR – number of log streams </li></ul></ul><ul><li>//STEP1 EXEC PGM=IXCL1DSU </li></ul><ul><li>//SYSPRINT DD * </li></ul><ul><li>//SYSIN DD * </li></ul><ul><ul><li>DEFINEDS SYSPLEX(PLXM) </li></ul></ul><ul><ul><ul><li>DSN(SYS1.LGR#PLXM.CDS01) VOLSER(BMCD03) </li></ul></ul></ul><ul><ul><ul><li>CATALOG </li></ul></ul></ul><ul><ul><li>DATA TYPE(LOGR) </li></ul></ul><ul><ul><ul><li>ITEM NAME(LSR) NUMBER(5) </li></ul></ul></ul><ul><ul><ul><li>ITEM NAME(LSTRR) NUMBER(10) </li></ul></ul></ul>
  61. 61. Define Log Streams <ul><li>Associate data sets, log stream names, structure names and attributes. </li></ul><ul><ul><li>Structures may be defined or deleted </li></ul></ul><ul><ul><li>Streams may be defined, deleted or updated </li></ul></ul><ul><li>//STEP1 EXEC PGM=IXCMIAPU </li></ul><ul><li>//SYSIN DD * </li></ul><ul><ul><li>DATA TYPE(LOGR) REPORT(YES) </li></ul></ul><ul><ul><li>DEFINE STRUCTURE NAME(LOGGER_OPERLOG) </li></ul></ul><ul><ul><ul><li>AVGBUFSIZE(512) </li></ul></ul></ul><ul><ul><ul><li>MAXBUFSIZE(4096) </li></ul></ul></ul><ul><ul><ul><li>LOGSNUM(5) </li></ul></ul></ul><ul><ul><li>DEFINE LOGSTREAM NAME(SYSPLEX_OPERLOG) </li></ul></ul><ul><ul><ul><li>STRUCTNAME(LOGGER_OPERLOG) </li></ul></ul></ul><ul><ul><ul><li>... </li></ul></ul></ul>
  62. 62. Update the CFRM Policy <ul><li>Update CFRM policy with names of the structures to be used by z/OS System Logger. </li></ul><ul><li>//STEP1 EXEC PGM=IXCMIAPU </li></ul><ul><li>//SYSIN DD * </li></ul><ul><ul><li>DATA TYPE(CFRM) REPORT(YES) </li></ul></ul><ul><ul><ul><li>. . . </li></ul></ul></ul><ul><ul><ul><li>DEFINE STR(LOGGER_OPERLOG) </li></ul></ul></ul><ul><ul><ul><li>SIZE(13568) </li></ul></ul></ul><ul><ul><ul><li>PREFLIST(C033,C021) </li></ul></ul></ul>
  63. 63. Automatic Restart Manager <ul><li>The Automatic Restart Manager (ARM) is an z/OS recovery function </li></ul><ul><ul><li>Improves the availability of specified subsystems and applications </li></ul></ul><ul><ul><li>Automatically restarting them as requested </li></ul></ul><ul><ul><li>Function of the Cross-System Coupling Facility (XCF) component </li></ul></ul><ul><ul><ul><li>Runs in XCF address space </li></ul></ul></ul><ul><ul><ul><li>Uses data spaces </li></ul></ul></ul><ul><ul><li>Augments the functions of production controllers, automation products, and job schedulers </li></ul></ul><ul><ul><li>Subsystems that use ARM are expected to perform their own transaction level and database recovery </li></ul></ul><ul><ul><li>Requires: </li></ul></ul><ul><ul><ul><li>ARM Couple data sets which have connectivity to all the systems on which ARM is active </li></ul></ul></ul>
  64. 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. 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. 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. 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)
  68. 68. ARM Policy - IXCMIAPU //IXCARMP0 JOB //STEP1 EXEC PGM=IXCMIAPU //SYSPRINT DD SYSOUT=A //SYSIN DD * DATA TYPE(ARM) DEFINE POLICY NAME(ARMPLXM1) RESTART_GROUP(DEFAULT) TARGET_SYSTEM(*) ELEMENT(*) RESTART_ATTEMPTS(0) RESTART_GROUP(VTAMGRP) TARGER_SYSTEM(*) ELEMENT(NET@V*) RESTART_ATTEMPTS(3,300) READY_TIMEOUT(900) TERMTYPE(ELEMTERM) /* IXCMIAPU Utility example

×