1 / 23

Chapter 7: Systems Management

Chapter 7: Systems Management. Objectives. Be able to: Understand system management disciplines Understand the different data types z/OS uses Understand how errors are handled. Introduction to systems management.

vevans
Download Presentation

Chapter 7: Systems Management

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Chapter 7: Systems Management

  2. Objectives Be able to: • Understand system management disciplines • Understand the different data types z/OS uses • Understand how errors are handled

  3. Introduction to systems management Systems management is a general term that is widely used, . Sometimes it means: - the operator interface, - means provisioning capacity. In a large-scale commercial system, “A collection of disciplines aimed to monitor and control a system’s behavior.”

  4. Introduction to systems management • Performance management • Workload management • Configuration management • Operations management • Problem management • Network management • Storage management • Security management • Change management

  5. System Data • Accounting • Reporting • Performance • Errors

  6. Z/OS component SMF (System Management Facilities) Collect info concerning: • Billing users • Reporting reliability • Analyzing the configuration • Scheduling jobs • Summarizing direct access volume activity • Evaluating data set activity • Profiling system resource use • Maintaining system security

  7. Data Collection in z/OS

  8. WorkLoad Management (WLM) WLM retains the following data: • CPU time used • Memory used + pages/sec • I/Os done + I/O rate • Transaction rate • Goal achievement

  9. Performance management Performance management includes measuring, analyzing, reporting, and tuning the performance of IT resources. Two categories: Real-time monitoring, alerting, problem identification, and problem resolution...What's happening NOW Bench marking, modeling, rerunning problem scenarios, and trending performance metrics to feed capacity planning...Where are we heading

  10. Performance management Objectives: • Optimize response time and throughput of IT resources • Take corrective actions to alerts and problem requests

  11. Performance management : z/OS implementation Resource Measurement Facility (RMF): • Batch monitoring • CPU • Storage • Workload • I/O Activity • Other • Online monitoring • Delay monitoring ...Queue wait time

  12. Configuration management In a large-scale commercial system, - the number of hardware devices, - system software items (compiled modules, source modules, data items, etc.), and - application software items have been large since the first days of the mainframe.

  13. System Software configuration management Characteristics: • Large number of components. • Great packing flexibility. • Backward compatibility need. • Different software developers and vendors. • Long-supported versions.

  14. System Software configuration management 4 types of SYSMODs: • PTF • APAR • FUNCTION • USERMOD

  15. Hardware configuration management Hardware Configuration Definition (HCD) : • It is written in a system file. • Is split between the hardware and the software. • Has to be tested. • Has to be activated sysplex-wide

  16. Application configuration management Application configuration management is a discipline that is common to any platform. On a IBM System z platform these tools must be able to manage Java (WebSphere Application Server) as well as COBOL applications. IBM’s tool is named Software Configuration and Library Manager (SCLM).

  17. Operations management Operations in a large-scale commercial operating system is crucial for performance and availability. Operations means 2 related activities: • Batch scheduling • Console operations

  18. Problem management Problem management is a discipline that can be viewed from various angles: • How problems are solved • How problems are reported • How problems are tracked

  19. Network management z/OS participates as any other node on the network and complies to the standards in this area On such networks, the z/OS network management subsystem usually acts as the focal point.

  20. Storage management • In z/OS the software that manages the external storage devices is called DFSMS. (Data Facility Storage Management Subsystem)

  21. Security management Legend BtB Users Policy Manager Policy Director Manager Intrusion Detection System INTERNET WebSeal TIVOLI SecureWay Directory Switch INTRANET WebSeal WebSeal Switch ... IDS LPAR DMZ Internet LPAR DMZ Internet LPAR DMZ Internet IBM System z FireWall FireWall FireWall Web Services Web Services Web Services Users Production LPAR VPN

  22. Change management Change management is a discipline that is -meant for the whole infrastructure. -z/OS manages changes applied to software through SMP/E asking for prerequisites and logging the changes.

  23. Summary • 9 system management disciplines • Service Level management (SLA) is not covered • Security management is special • Tools are available

More Related