Section 2B Parallel Sysplex

1937 days ago, 715 views
PowerPoint PPT Presentation
2. Targets. In this section you will figure out how to: Discuss a Sysplex Coupling Facility Describe a Parallel Sysplex Explain how Parallel Sysplex can accomplish nonstop accessibility Use dynamic workload adjusting Explain the single framework picture Describe asset modification crosswise over Systems in a Sysplex .

Presentation Transcript

Slide 1

Part 2B Parallel Sysplex

Slide 2

Objectives In this section you will figure out how to: Discuss a Sysplex Coupling Facility Describe a Parallel Sysplex Explain how Parallel Sysplex can accomplish nonstop accessibility Use dynamic workload adjusting Explain the single framework picture Describe asset change crosswise over Systems in a Sysplex Note to educator : Some slides are vivified - Use Power Point slide demonstrate Only ~ 20 slides to show – the rest are additional

Slide 3

Basic v.s. Parallel Sysplex (SYStems comPLEX) September 1990, IBM appeared the SYSPLEX presenting XCF administrations permitting approved applications to speak with applications on the same or different frameworks utilizing specific connections. Fundamental – A mutual couple informational collection utilized between every one of the pictures holds control data and gives a component to checking the status of the pictures Parallel – This upgraded sysplex usage gave the ability to utilize an a specific LIC working condition called the coupling office control code (CFCC) offering rate and trustworthiness to shared information. While a fundamental sysplex is a genuine substance, with a characterized name (the sysplex name), a parallel sysplex is more theoretical, that is an arrangement of frameworks with in a sysplex that all have admittance to a similar at least one coupling offices * . * Described later in slides

Slide 4

SYS tems com PLEX or SYSPLEX z/OS Images z/OS Images z/OS Images z/OS Images 32 z/OS Images z/OS Images z/OS Images z/OS Images z/OS Images z/OS Images z/OS Images

Slide 5

Sysplex Goal is a Single System Image

Slide 6

Provides diminished cost through: Cost compelling processor innovation IBM programming authorizing charges in Parallel Sysplex Continued utilization of vast framework information handling aptitudes without re-instruction Protection of z/OS application ventures The capacity to deal with an expansive number of frameworks more effectively than other similarly performing multisystem conditions What a Sysplex can accomplish for YOU… It will address any of the accompanying sorts of work: Large business issues that include several end clients, or manage volumes of work that can be tallied in a great many exchanges for each day. Work that comprises of little work units, for example, online exchanges, or extensive work units that can be subdivided into littler work units, for example, inquiries. Simultaneous applications on various frameworks that need to straightforwardly get to and refresh a solitary database without risking information trustworthiness and security.

Slide 7

What else a Sysplex can accomplish for YOU ! Stage for consistent accessibility with the goal that applications can be accessible 24 hours a day, 7 days seven days, 365 days a year Ability to accomplish more work Greater limit Improved capacity to oversee reaction time Platform for further limit and reaction time propels Greater adaptability Ability to blend levels of equipment and programming Ability to powerfully include frameworks A simple way for incremental development Varied stages for applications, including parallel, open, and customer/server Workload adjusting

Slide 8

Sysplex Anatomy A sysplex can incorporate the accompanying programming and equipment: 1. z/OS Products incorporate the cross-framework coupling office (XCF) segment, which empowers approved projects in a sysplex to speak with projects on similar MVS framework or different MVS frameworks and the worldwide asset serialization part, which serializes sysplex assets. 2. Flagging ways between z/OS frameworks - There must be no less than two operational flagging ways (one inbound and one outbound way) between each of the zOS frameworks - The flagging ways can be characterized through: * Coupling office list structures * ESCON or FICON diverts working in CTC mode * 3088 Multisystem Channel Communication Unit 3. Sysplex couple informational collection z/OS requires a DASD informational index - Shared by all frameworks in the sysplex. - Sysplex couple informational collection, z/OS stores data identified with the sysplex, frameworks, XCF bunches Ŧ , and their individuals. CF Ŧ A XCF gathering is the arrangement of related individuals that a multisystem application characterizes to XCF. A multisystem application can be an establishment characterized program, a zOS part or subsystem, or a program item. In any case, you can characterize a solitary framework sysplex that does not require a sysplex couple informational index.

Slide 9

Sysplex Anatomy… proceeded with 4. Basic time reference When the sysplex comprises of numerous zOS frameworks running at least two processors, zOS requires that the processors be associated with the same Sysplex Timer. - zOS utilizes the Sysplex Timer to synchronize TOD tickers crosswise over frameworks. - For a multisystem sysplex characterized on a solitary processor (under PR/SM™ or VM) the SIMETRID parameter in the CLOCKxx parmlib part should indicate the recreated Sysplex Timer identifier to synchronize timings for the zOS frameworks. TOD Clocks: In a design with more than one CP, each CP may have a different TOD clock (as in the zOS' Parallel Sysplex) or more than one CP may have a similar clock. To aid the synchronization of the TOD checks in a multisystem sysplex, another architected 128-piece augmented time-of-day clock is accessible. The stretched out clock organization was required to give the enhanced determination important to the quicker z10 processors as they get to be distinctly accessible. The expanded time-of-day design guarantees that when an application in a multisystem sysplex condition asks for a TOD esteem, XCF will dependably give back a clock esteem that is interesting over the sysplex, paying little respect to the quantity of frameworks in the sysplex.

Slide 10

Sysplex Coupling Facility - The paste for cross framework information correspondence Within the Coupling Facility, stockpiling is progressively parceled into structures. z/OS administrations control information inside the structures. Each of the accompanying structures has an exceptional capacity: Cache structure : Supplies a component called cushion negation to guarantee consistency of stored information. The reserve structure can likewise be utilized as a rapid support for putting away imparted information to normal read/compose get to. List structure : Enables approved applications to share information that is sorted out in an arrangement of records, for executing capacities, for example, shared work lines and shared status data. Bolt structure: Supplies shared and elite locking capacity for serialization of shared assets down to a little unit of information. IBM delineations and outlines symbolizes a Coupling Facility (CF) utilizing a triangle

Slide 11

Exploiters of the Coupling Facility (CF) Authorized Applications Information Management System Database (IMS DB) Database 2 (DB2) Virtual Storage Access Method

Slide 12

z/OS Resource Sharing Later designs Earlier arrangements

Slide 13

System z Sysplex Resource Sharing This is not to be mistaken for application information sharing This is sharing of physical framework assets, for example, tape drives, indexes, reassures This abuse is incorporated with z/OS Simplifies the administration of the framework

Slide 14

Console Sharing in Sysplex

Slide 15

Resource Sharing by means of Coupling Facility

Slide 16

What is Parallel Sysplex Builds on the quality of System z servers by connecting up to 32 pictures to make the business' most effective advertisement handling grouped framework Every "cloned" application can keep running on each picture Hardware and programming can be kept up non-problematically Innovative multi-framework information sharing innovation Direct simultaneous read/compose access to shared information from all preparing hubs No loss of information trustworthiness No execution hit Transactions and questions can be dispersed for parallel execution in view of accessible limit and not confined to a solitary hub

Slide 17

Parallel Sysplex

Slide 18

Applications " SAME " Applications Parallel Sysplex Loosely coupled multiprocessing Hardware/programming blend Requires: Data sharing Locking Cross-framework workload dispatching Synchronization of time for logging, and so forth. Rapid framework coupling Hardware: Coupling Facility Integrated Cluster Bus and ISC to give fast connections to CF Sysplex Timer – Time Of Day check synchronization Implemented in z/OS* and subsystems Workload Manager in z/OS Compatibility and misuse in programming subsystems, including IMS*, VSAM*, RACF*, VTAM*, JES2*, and so on - Rolling Maintenance System and Application Code System Z9

Slide 19

Continuous accessibility Within a parallel sysplex group, it is conceivable to develop a domain with no single purpose of disappointment Peer occurrences container of a coming up short subsystem can assume control recuperation obligation regarding assets held by the coming up short occasion Alternatively the coming up short subsystem can be consequently restarted on still sound frameworks In a parallel sysplex it is conceivable that the passing of a server might be straightforward to the application and the server workload redistributed naturally with little execution corruption Each framework is still individual Software redesigns can be moved through one framework at any given moment on a sensible timescale for the business

Slide 20

Applications in a Parallel Sysplex Design objective of no application changes Benefits Scalability Integration of more seasoned applications with new workloads, for example, web presenting With a current sysplex there is next to no foundation work required for another application. The current framework may even be utilized without the requirement for another server

Slide 21

Policy Based Implementation Note: The External Time Reference (ETR) utilized by the diverse frameworks

Slide 22

Sysplex - Works with a Policy An approach is an arrangement of principles and activities that frameworks in a sysplex are to take after when utilizing certain zOS administrations. A strategy permits zOS to oversee frameworks particular assets in complianc