RRN 07516 DUR MANAGEMENT: DISPLAY ALL DURS

ALTKWH02

Message Triggering Condition

Response in case of successful/unsuccessful result of the execution, on operator request to display the DUR information using the option DISPLAY with the parameter ALLDURS (with or without one of the parameters; DLSID, CETYPE, LCEID, APT or GPT), wherein the parameters TABLE and RELATION were not given, via the following MMC-command :
CRN 07678 MANAGE-DURS

Report Layout

 SWA-I/O CENTRAL
    (A).......................                   (B).................
                                 (C)........................... (D) (E)
    -----------------------------------------------------------------
        DISPLAY                                     (1) SUCCESSFUL
        ----------------------------------------------------------
        (3)............ (4)..... (5)..        FMM ENTRY = (6)
        (7)...........................   (8)..
        DLS ID    =   (9)..
        LCE ID    =   (10)..
        CE TYPE   = (11) (12)....
        APT       = (13) (14)....
        GPT       = (15) (16)....
        FROM DATE = (17) (18)......
        TO DATE   = (19) (20)......
        (21).......................................................
        (22).......................................................
        (23)....  (24)............  (25)......  (26)............
  REPORT REFERENCE NUMBER = 7516

Parameter Identification

Par. No. Meaning Remarks
(A) Command name
(B) Main execution result
(C) Result part type
(D) Result part number
(E) Continuation indicator
(1) Completion code
NOT displayed in case of not
successful execution
(3) Error type see Evaluation 000000000000000000
- the parameters; (2) to (7) are
displayed in error cases,
otherwise they are suppressed
(4) Error location_place indicator (in case of GIO error)
IN FILE error occurred in the file
specified with the parameter (4)
(5) Error location_place no (in case of
GIO error)
logical file identity where the error occurred
(6) FMM entry number location in the Disk Update
Facility (DUF) FMM where the
error has been generated
(7) Error description see Evaluation
(8) Error code can be either; 0000000000
- data base status (see SI057), 000
- record size, or 000000000000000000
000000000000000000000000000000000 in case of data base error 000000 in case of GIO error: 'INVALID
00000000000000000000000000000000000
- I/O sub-code (see SI 058)
RECORD SIZE' 00000000000000000000 in case of GIO errors: 'OPEN
FAILURE' or 'READ'
(9) Data Load Segment (DLS) identity the display of the parameters;
(8) to (14) depends on the input
parameters used in the
MMC-command
(10) Logical control element identity in hexadecimal format
(11) Control element type see SI 210
(12) Control element type see SI 210
(13) Application processor type see SI 210
(14) Application processor type see SI 210
(15) Generic processor type see SI 210
(16) Generic processor type see SI 210
(17) Implementation start date year month day
(18) Implementation start date year month day
(19) Implementation end date year month day
(20) Implementation end date year month day
(21) Title for the displayed DUR information
DUR DATE/TIME RELATION TABLE -
(22) Underlines for the title
(23) Data Update Request (DUR) name
(24) Date/time of implementation for the involved DUR name
(25) Relation name for which the DUR was written
(26) Data base control table for which the DUR was written

Evaluation

Key Parameter Contents / Meaning Action
1 2 3
(3) DB ERROR . . . . . . . . . . . . . . . . . . . . .
(7) GET R-LCESWCD1 . . . . . . . . . . . . . . . . . . A
(7) GET R-LPT-DES1 . . . . . . . . . . . . . . . . . . A
(7) GET R-RELDCR . . . . . . . . . . . . . . . . . . . A
(7) GET R-USERFILE . . . . . . . . . . . . . . . . . . A
(3) GIO ERROR . . . . . . . . . . . . . . . . . . . .
(7) INVALID RECORD SIZE . . . . . . . . . . . . . . . B
(7) OPEN FAILURE . . . . . . . . . . . . . . . . . . . B
(7) READ FAILURE . . . . . . . . . . . . . . . . . . . B
(3) INPUT ERROR . . . . . . . . . . . . . . . . . . .
(7) DUR NOT FOUND . . . . . . . . . . . . . . . . . . C
(7) INDEX FILE EMPTY . . . . . . . . . . . . . . . . . C

Action Description

Action Meaning
A Data base error occurred for the given relation. See also FMM entry point and data base status (parameter 7) to identify the problem.

Special fault clearing is necessary. See fault reporting procedures. Refer to the document FAULT REPORTING PROCEDURES which is part of the Customer Documentation Guide.

B A General Input/Output error occurred. See also FMM entry point, file identity (parameter 4) that the error occurred and the error code (parameter 7) to identify the problem.

Special fault clearing is necessary. See fault reporting procedures. Refer to the document FAULT REPORTING PROCEDURES which is part of the Customer Documentation Guide.

C The meaning of the input errors are as follows :
  • DUR NOT FOUND : the DUR name entered in the MMC-command was not found in the index file.
  • INDEX FILE EMPTY : no DURs were found in the index file.

Correct the input data and enter the MMC-command again. See also Restrictions part of the corresponding MMC-command.

If the input data is correct, the given result data can be taken as information only.