Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Method For Intelligently Reducing The Amount Of Storage Required In A Dump Based On The Location In Storage Where The Problem Occurred, And Reducing It Further By Dumping Storage That Is Owned By A Failing application

IP.com Disclosure Number: IPCOM000033031D
Original Publication Date: 2004-Nov-22
Included in the Prior Art Database: 2004-Nov-22
Document File: 1 page(s) / 58K

Publishing Venue

IBM

Abstract

Method for intelligently reducing the amount of storage required in a dump based on the location in storage where the problem occurred, and reducing storage further by dumping storage that is owned by a failing application.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 100% of the total text.

Page 1 of 1

Method For Intelligently Reducing The Amount Of Storage Required In A Dump Based On The Location In Storage Where The Problem Occurred, And Reducing It Further By Dumping Storage That Is Owned By A Failing application

With the 64-bit architecture allowing more than 2 gigabytes (GB) of memory, a method is needed to reduce the amount of storage that is dumped when a problem occurs. When we are dumping, the system is paused, preventing users from doing work during that time frame. The solution is to select the areas of storage to be dumped based on the location where the failure occurred.

    This method works by having a core resident table that contains the address range and a list of the storage that should be dumped when a problem occurs in that area. The areas to dump are given names that map to storage areas in another table. We also have an owner field that allows the dumping of storage that belongs to a named application. The core resident table can be updated by an operator command or a control program load.

    In the example that follows, if a program check occurred in locations 3000 to 10000, we would dump only the blocks that belong to the TAPE application.

Storage area Areas to dump

3000 - 10000 Work blocks

1