IBM z/OS系统编程ABC第10卷：深入主机技术

需积分: 3 114 浏览量更新于2024-08-01 收藏 8.21MB PDF 举报

"ABCs of zOS System Programming Volume 10 是一本由IBM出版的关于主机系统编程的书籍，主要涵盖了z/OS操作系统、CICS、JCL和VSAM等主题。书中详细介绍了z/Architecture（IBM System z的处理器设计和连接性）、LPAR概念、HCD、z9和z10处理器以及DS8000 DASD控制器的相关内容。该资源可以在IBM官方网站的redbooks部分找到。" 本文详细解析了《ABCs of zOS System Programming Volume 10》中涉及的关键知识点： 1. **z/Architecture**： - z/Architecture是IBM大型主机系统的核心架构，它定义了处理器的硬件特性、内存管理和I/O操作等。在本书中，这部分内容可能涵盖64位地址空间、虚拟存储系统、并行处理能力以及对高级语言的支持。 2. **IBM System z**： - IBM System z是IBM的一系列大型主机产品，包括z9和z10等不同型号。这些系统通常用于处理大量交易和数据密集型应用，具有高度的可靠性和安全性。 3. **LPAR (Logical Partition)**： - LPAR是一种在单个物理主机上创建多个独立虚拟环境的技术。每个LPAR可以运行不同的操作系统实例，实现资源隔离和优化。书中可能讲解了如何配置和管理LPAR，以及其对性能和可用性的影响。 4. **HCD (Hardware Configuration Dataset)**： - HCD是定义z/OS系统硬件配置的组成部分，包括I/O设备、网络设置等。学习HCD有助于理解如何正确配置和管理主机系统的硬件资源。 5. **DS8000 DASD Controller**： - DS8000是IBM的一种高性能磁盘存储系统，DASD（Direct-Access Storage Device）控制器是连接主机与存储设备的关键组件。这部分可能涉及DS8000的特性、性能优化和故障排除。 6. **CICS (Customer Information Control System)**： - CICS是IBM开发的一个在线事务处理监控系统，常用于处理银行、零售等行业的实时业务交易。书中可能介绍了CICS的基本概念、编程模型和日常管理。 7. **JCL (Job Control Language)**： - JCL是z/OS系统中的作业控制语言，用于定义和调度主机上的作业流程。读者可以学习如何编写和优化JCL脚本以提高效率。 8. **VSAM (Virtual Storage Access Method)**： - VSAM是IBM的访问方法之一，提供了高效的数据存取方式。这部分可能涵盖VSAM文件结构、数据访问优化和性能监控。此外，书中还可能包含实践案例、故障排查技巧和最佳实践，帮助读者深入理解和应用这些技术。对于想在IBM大型主机环境中工作的系统程序员或管理员来说，这是一份宝贵的参考资料。

xiv ABCs of z/OS System Programming Volume 10

Thanks to the following people for their contributions to this project:

Alvaro Salla is an IBM retiree who worked for IBM for more than 30 years, specializing in

large systems. He has co-authored many IBM Redbooks publications and spent many years

teaching about large systems from S/360™ to S/390®. He has a degree in Chemical

Engineering from the University of Sao Paulo, Brazil.

Thanks to the authors of the previous editions of this book.

򐂰 Authors of the previous editions, ABCs of z/OS System Programming Volume 10,

published in August 2004, 2006, and 2007, were:

Alvaro Salla

Livio Sousa is a Technical Sales Support member of the Linux® for zSeries team in Brazil.

He has four years of experience in the areas of operational systems and networking. He is

finishing college and has been working for IBM since 2002, with responsibility for planning

and implementing new workload projects. He has been a contributor to other IBM Redbooks

publications.

Thanks also to Robert Haimowitz, International Technical Support Organization,

Poughkeepsie Center, for his support of this project.

The second and third editions of this book were produced by the following specialists working

at the International Technical Support Organization, Poughkeepsie Center:

Paul Rogers

Alvaro Salla

Become a published author

Join us for a two- to six-week residency program! Help write a book dealing with specific

products or solutions, while getting hands-on experience with leading-edge technologies. You

will have the opportunity to team with IBM technical professionals, Business Partners, and

Clients.

Your efforts will help increase product acceptance and customer satisfaction. As a bonus, you

will develop a network of contacts in IBM development labs, and increase your productivity

and marketability.

Find out more about the residency program, browse the residency index, and apply online at:

ibm.com/redbooks/residencies.html

Comments welcome

Your comments are important to us!

We want our books to be as helpful as possible. Send us your comments about this book or

other IBM Redbooks in one of the following ways:

򐂰 Use the online Contact us review Redbooks form found at:

ibm.com/redbooks

Chapter 1. Introduction to z/Architecture

In this chapter, we provide an overview of z/Architecture.

z/Architecture is the next step in the evolution from System/360™ to System/370™,

System/370 Extended Architecture (370-XA), Enterprise Systems Architecture/370™

(ESA/370), and Enterprise Systems Architecture/390 (ESA/390). In order to understand

z/Architecture, you have to be familiar with the basics of ESA/390 and its predecessors.

address space maps all of the available addresses—and includes system code and data,

as well as user code and data. Thus, not all of the mapped addresses are available for user

code and data. This limit on user applications was a major reason for System/370 Extended

Architecture (370-XA) and MVS/XA™. Because the effective length of an address field

expanded from 24 bits to 31 bits, the size of an address space expanded from 16 megabytes

to 2 gigabytes. An MVS/XA address space is 128 times as big as an MVS/370 address

space.

In the early 1980s, XA (or extended architecture) was introduced with an address space that

began at address 0 and ended at two gigabytes. The architecture that created this address

space provided 31-bit addresses. To maintain compatibility, MVS™ provided two addressing

modes (AMODEs) for programs: programs that run in AMODE 24 can use only the first 16

megabytes of the address space, and programs that run in AMODE 31 can use the entire 2

gigabytes.

As of z/OS V1R2, the address space begins at address 0 and ends at 16 exabytes, an

incomprehensibly high address. This architecture, zArchitecture, in creating this address

space, provides 64-bit addresses. The address space structure below the 2 gigabyte address

has not changed; all programs in AMODE 24 and AMODE 31 continue to run without change.

In some fundamental ways, the address space is much the same as the XA address space.

z/OS and the IBM zSeries 900 (z900) deliver the 64-bit architecture (z/Architecture) to

provide qualities of service that are critical for the e-business world. 64-bit real storage

support eliminates expanded storage and helps eliminate paging. 64-bit real storage support

may allow you to consolidate your current systems into fewer logical partitions (LPARs), or to

a single native image.

剩余527页未读，继续阅读

sdis15

粉丝: 0
资源: 21

IBM z/OS系统编程ABC第10卷：深入主机技术

ABCs of zOS System Programming Volume1.pdf

ABCs of zOS System Programming Volume 1

ABCs of zOS System Programming Volume 13

DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated since Python 3.3, and in 3.10 it will stop working from collections import Iterable

from torch._six import container_abcs

deprecationwarning: using or importing the abcs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working from collections import mapping, defaultdict

ImportError: cannot import name 'container_abcs' from 'torch._six' (D:\anaconda3\envs\pytorch\lib\site-packages\torch\_six.py)

cannot import name 'container_abcs' from 'torch._six'

最新资源