Pre-Grant Publication Number: 20100268561
Please help the USPTO examine the application by evaluating the relevance of the publicly submitted prior art to the patent application.
Peer To Patent forwards the Top 10 most relevant prior art submissions and their annotations to the USPTO.
Review this prior art and click on the thumbs up (or down) to indicate whether this submission should be forwarded to the USPTO.
If you login then you can add an annotation by typing in the box at the bottom of the screen to comment on the relevance of the prior art to the claims of the patent application.
Review this prior art and click on the thumbs up (or down) to indicate whether this submission should be forwarded to the USPTO.
If you login then you can add an annotation by typing in the box at the bottom of the screen to comment on the relevance of the prior art to the claims of the patent application.
Prior Art Detail
Summary / Description
| Summary / Description | The granddaddy of all computer systems architecture and this Redbook does and excellent job of discribing it. |
Basic Information
| Type of Prior Art | Online Publication |
| URL | http://www.redbooks.ibm.com/red... |
| Author/Creator | Mike Ebbers, Wayne O'Brien, Bill Ogden, et al |
| Title | Introduction to the New Mainframe: z/OS Basics |
| Publication Date | January 1, 2004 |
| Publisher | IBM Redbooks |
| Directions to Document Location | |
| Additional Information | |
Notes / To Do
| Notes | |
Excerpt
Excerpt "An extensive set of system facilities and unique attributes makes z/OS well suited for processing large, complex workloads, such as those that require many I/O operations, access to large amounts of data, or comprehensive security. Typical mainframe workloads include long-running applications that update millions of records in a database and online applications that can serve many thousands of users concurrently."
"An address space describes the virtual storage addressing range available to a user or program.
The address space is an area of contiguous virtual addresses available to a program (or set of programs) and its data requirements. The range of virtual addresses available to a program starts at 0 and can go to the highest address permitted by the operating system architecture. This virtual storage is available for user code and data.
Because it maps all of the available addresses, an address space 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.
Two types of physical storage are available: central storage and auxiliary storage (AUX). Central storage is also referred to as real storage or real memory.
The Real Storage Manager (RSM™) controls the allocation of central storage during system initialization, and pages1 in user or system functions during execution.
The auxiliary storage manager controls the use of page and swap data sets. z/OS moves programs and data between central storage and auxiliary storage through processes called paging and swapping.
z/OS dispatches work for execution (not shown in the figure). That is, it selects programs to be run based on priority and ability to execute and then loads the program and data into central storage. All program instructions and data must be in central storage when executing.
An extensive set of facilities manages files stored on direct access storage devices (DASDs) or tape cartridges.
Operators use consoles to start and stop z/OS, enter commands, and manage the operating system.
z/OS is further defined by many other operational characteristics, such as security, recovery, data integrity and workload management."
|
Relevance
Claims
1
Relevance
Z/OS is a well defined enterprise architecture that is fully operational in many large scale data centers througout the world. There are hundreds of millions of lines of working code that execute within Z/OS that allow hundreds, if not thousands, of applications to process massive workloads concurrantly without regard to each other and without interferring with each other; all following the architectual rules.
There is nothing novel or non-obvious about this claim.
Z/OS is a well defined enterprise architecture that is fully operational in many large scale data centers througout the world. There are hundreds of millions of lines of working code that execute within Z/OS that allow hundreds, if not thousands, of applications to process massive workloads concurrantly without regard to each other and without interferring with each other; all following the architectual rules.
There is nothing novel or non-obvious about this claim.
Claim Chart
All
0 days left
