Input From CMS Notes Module
1 Prompt user to find out if this activity DMMPRO is to create a new problem report or to
update an existing report.
2 A response of 'NO' to this prompt DMMPRO indicates this is a new problem. The user is prompted for the date I I and time of the failure, the SCP, CPU type, CPU serial, and other
generai information. The user is prompted for the
category of the problem; for example, abend message or loop. The user is prompted for detailed information, depending on the
type of failure. The user is prompted for additional user comments.
Processing
Prompt user to determine if this
is a new or an existing problem. If a duplicate problem, reflect it in symptom summary.
2 For a new problem: Obtain general report
information. Determine category of failure. Prompt for specific informa· tion about the faiiure. Obtain additional user
comments in free form text.
Label Ref Notes EXIST MAINLINE I I GETFAIL TEXTENTR
Output
to Step 3
Module Label Ref I I Diagram 2-3. PROB IPCS Command (Part 1 of 2)
Chapter 2z IPCS--The Interactive problem Ccntrcl System 25
Input r REG 1 ______ ..,
Parameter
List
Notes
3 The date and time stamps are supplied
from CMS low storage. The
FSWRITE routine writes the first two
records, which contain general information about the problem. The
third record, containing a start of
keyword area indicator, is written. Keyword data is passed in variable blocked format. The data is
extracted and moved to the output
buffer one entry per 80-character
record. FSWRITE adds this data
and an end of keywords record. Supplementary data file names
are added to the problem report
file if supplied. Textual descriptions of the problem are added to the file if supplied. . Data from INTSECT (the internal
data area) low storage (time and
date) and the initial status fields are
moved to the 80-byte output area
and FSWRITE adds the data to the
symptom summary file. The keyword data is rounded up to
a multiple of 80 bytes and the
information is added to the symptom
summary file. From
Diagram
2-5 Module DMMWRT
Output
3 Write a problem report.
4 Look for duplicate problem. 5 For an existing problem: Obtain the problem number
from the user. Obtain any additional
supporting data file
information. Obtain any user free form
comments to be added. Return
to CMS Add information to the
problem report. Label Ref Notes
4 Look for duplicate problem: The keyword data for the new INTOUT problem is compared to that of all existing problems and any exact
matches are considered duplicates.
The search is terminated when the
newly created problem is
encountered. KEYOUT The user is notified (at the terminal) as each duplicate problem is
encountered. Up to 10 duplicate
problems may be displayed for a
search. SUPPOUT If duplicate was found, DMMSUM
is called to record the first
encountered duplicate problem TEXTOUT
number in both the symptom
summary control record for the
problem, and the problem report.
CNTRLOUT
5 A response of 'YES' to the prompt
indicates that this is an update to an
existing problem: The user is prompted for the number
of the problem, and its existence is
CNTRLOUT verified. The user is prompted for any
additional data file names. The user is prompted for free form
comments to be added to the report. The new information, with a date
and time stamp is added to the problem report.
Diagram 2-3. PROB IPCS Command (Part 2 of 2)
26 IBM VM/370 Service Routines Program Logic Module Label Ref
DMMSEA START
PUTOUT
ENDRTN
DMMPRO OLDPROB GETSDATA
TEXTENTR
OLDADD
Previous Page Next Page