Browse Prior Art Database

Automation of Operator Interface During Dump Invocation

IP.com Disclosure Number: IPCOM000046095D
Original Publication Date: 1983-May-01
Included in the Prior Art Database: 2005-Feb-07
Document File: 2 page(s) / 13K

Publishing Venue

IBM

Related People

Ewing, DJ: AUTHOR [+4]

Abstract

Problems that could be introduced into a stand-alone dump by operator error are eliminated by automating certain steps which used to be performed by an operator.

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

Page 1 of 2

Automation of Operator Interface During Dump Invocation

Problems that could be introduced into a stand-alone dump by operator error are eliminated by automating certain steps which used to be performed by an operator.

When it is necessary to take a stand-alone dump (SAD) of MVS (Multiple Virtual System), the operator has the responsibility of initiating an external "store status" operation prior to loading the SAD program. In an MP (multiprocessing) environment, this status operation must be performed for the processor on which SAD is loaded. The status of other processors in an MP environment is secured by SAD via the SIGP instruction with a Stop/Store Status order code.

The status stored as a result of this action provides the subsequent dump with crucial processor state data required by the debugger. Without this data, analysis of the dump is extremely limited as the debugger is seldom able to reconstruct the system activity at the time of failure.

This operation is susceptible to being plagued by one of two operator problems. The first occurs if the operator of an MP system initiates "store status" on all processors with the last processor being other than the one on which SAD is loaded. This action results in a status-processor mismatch which is flagged in the dump as a "no status" condition. The second problem occurs if the operator does not initiate "store status". As in the previous problem, a mismatch is detected and appropriately flagged.

The following sequence involving the maintenance support and service facility (MSSF) and the system control program (SCP) will enhance the stand- alone dump procecure by removing operator dependencies.

1. MVS, during its initialization process, will set a

new indicator to be processed by the MSSF. The

indicator will be located in the SCP flags or data

area passed...