Browse Prior Art Database

Method of obtaining diagnostic data associated with a specific operator message

IP.com Disclosure Number: IPCOM000015109D
Original Publication Date: 2002-May-21
Included in the Prior Art Database: 2003-Jun-20
Document File: 2 page(s) / 50K

Publishing Venue

IBM

Abstract

Disclosed is a method which allows a system programmer (or debugger) to gather diagnostic data when an operator message (referred to as a WTO in z/OS*) is issued by some program. An operator message may be the only symptom of some system problem and is often the only or first clue that a system debugger has when initially trying to diagnose the problem.

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

Page 1 of 2

Method of obtaining diagnostic data associated with a specific operator message

Disclosed is a method which allows a system programmer (or debugger) to gather diagnostic

data when an operator message (referred to as a WTO in z/OS*) is issued by some program.

An operator message may be the only symptom of some system problem and is often the only

or first clue that a system debugger has when initially trying to diagnose the problem.

SLIP is an z/OS* operator command that provides the ability the take a dump, cut trace records or wait state (stop) the system when various system events such as abends, memterms or PER interrupts occur. A new MSGID keyword has been added to the SLIP command to provide the ability to trap on an operator message. The message id of a message is defined as the first 10 characters or the characters up to the first blank - whichever comes first. The MSGID keyword allows the operator to specify the message id of the message that he is interested in trapping on.

      When a SLIP trap with the MSGID keyword is enabled, the WTO processor will give control to the SLIP exit when any WTO is issued. The exit will set up recovery and determine whether the MSGID in the WTO matches the MSGID in a SLIP trap. The case where there is only one enabled SLIP trap with the MSGID keyword is optimized by putting the MSGID in a control block that exists for the life of the ipl and thus can be accessed without any special serialization. Otherwise, the SLIP exit must serialize on SLIP control elements and search for traps which contain the MSGID keyword. When the MSGID in the message matches the MSGID keyword on some SLIP trap, the exit abends with a unique abend code, driving control into the Recovery Termination Manager of z/OS*. As part of the Recovery Termination Manager's processing, it will give control to the SLIP action processor to determine whether any error SLIP trap matches. The SLIP action processor will then check each error SLIP trap, including any traps with the MSGID keyword, to determine whether there is a match and will stop at the first one that matches, processing the specified ACTION keyword for that trap. This check fil...