Browse Prior Art Database

IBM System/390 I/O Call Reporting Process

IP.com Disclosure Number: IPCOM000103625D
Original Publication Date: 1993-Jan-01
Included in the Prior Art Database: 2005-Mar-18
Document File: 6 page(s) / 182K

Publishing Venue

IBM

Related People

Derr, A: AUTHOR [+3]

Abstract

Disclosed is a process which allows IBM maintained System/390 (S/390*) DASDs to be serviced as they are today with the Service Director solution, but eliminates the need for an extra PC and TSO support in the customer account. The process uses the 9221 Processor Console to receive and analyze Service Information Messages (SIMs) that would have been routed to Service Director in the current solution. After the 9221 Processor Console receives and analyzes the SIM, it displays the results to the customer. If a service call is required, the 9221 Processor Console will route the analysis results to the I/O controller's Product Application Program (PAP) in RETAIN. The 9221 Processor Console also provides problem management facilities for the I/O controller such as NetView* alerts and a Service History log.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

IBM System/390 I/O Call Reporting Process

       Disclosed is a process which allows IBM maintained
System/390 (S/390*) DASDs to be serviced as they are today with the
Service Director solution, but eliminates the need for an extra PC
and TSO support in the customer account.  The process uses the 9221
Processor Console to receive and analyze Service Information Messages
(SIMs) that would have been routed to Service Director in the current
solution.  After the 9221 Processor Console receives and analyzes the
SIM, it displays the results to the customer.  If a service call is
required, the 9221 Processor Console will route the analysis results
to the I/O controller's Product Application Program (PAP) in RETAIN.
The 9221 Processor Console also provides problem management
facilities for the I/O controller such as NetView* alerts and a
Service History log.

      Refer to Figs. 1-5 for the following description of the S/390
I/O call reporting process.

      When an I/O error occurs within an I/O controller or its
attached devices, the I/O controller issues a SIM to the system Error
Recovery Program (ERP).  When a service action point is reached due
to the error, the system ERP appends additional system data to the
SIM and creates an A3 record.  The system ERP then issues an SCLP
(Service Call Logical Processor) request to the System Control
Program (SCP).  The SCP executes the SCLP instruction with an event
type of Problem Management.

      Once the SCLP instruction is executed by the SCP, the A3 record
is routed to the Processor Console by the Processing Unit.  The
Processor Console SCLP Event Manager then identifies the event type
and passes the notification to the Problem Management Event Handler.
The processor issues an external interrupt to the SCP at the
completion of the A3 record transfer to the Processor Console.

      The Problem Management Event Handler interrogates the Problem
Management event data to see if it is an A3 record.  If it is
identified as an A3, the Processor Console Log Manager is called to
log the record.  Problem Analysis is then called as a result of this...