Input REG 1
Parameter
List
Notes
1 Check the first two operands (which
may be in any order) as entered, swap
them and check again. Issue error
messages for invalid input.
2 Call SUMMARY module (DMMSUM).
The following routines supply information appropriate to the
user's request:
- PTFON - DSPLY - PTFIS - IBM - CLOSE - USER - DUPOF - NEEDINFO - APAR -HELP
- SEV A. Pass input to parameter list pointed
to by register 1. The parameter list is:
Byte. Contents 1·8 Not used 9·16 P R Bnnnnn (problem
number) 17·24 Request type: UPST AT -Update status
UPFUNCT -Update last function UPSEV - Update severity
UPPTF -Update PTF
information
UPDUP -Update
duplicate information
UPAPAR -Update APAR
information 25·32 Update specific informa· tion.
From CMS Module
PRB DMMSUM Diagram 2-2. PRB IPCS Command
Processing Output
1 Check user options.
2 Invoke SUMMARY module to
execute request.
A. Get master record for
specified problem number.
B. Update and rewrite the
record. C. Indicate status update in
problem report and inform
user of operation
completion. CMS Label Ref Notes
-RETRY B. All activities cause "LAST" date to
be updated with the current date. C. After the status is updated in
the symptom summary file, append
the date and time and new status to
the problem report for history
purposes. The SUMMARY module supplies a return code which is
checked. If zero, an informational
reply is issued indicating
successful completion. If the
completion code is not zero, an
informational reply is issued
indicating that the update was unsuccessful. START 24 Service Routines Program Logic
o
o DMMSUM100S DMMSUM200S DMMSUM501S DMMSUM502S Module Label
DMMSUM REPORT1
PRB
Ref
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
Previous Page Next Page