| CRN 07678 | MANAGE-DURS |
SWA-I/O CENTRAL
(A)....................... (B).................
(C)........................... (D) (E)
-----------------------------------------------------------------
DISPLAY (1) SUCCESSFUL
------------------------------------------------------------------
(3)............ (4)..... (5).. FMM ENTRY = (6)
(7)........................... (8)..
DUR = (9) (10)....
(11).......................................................
(12).......................................................
(13)............ (14)...... (15)............ (16). (17)....
REPORT REFERENCE NUMBER = 7517
| 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 Update Request (DUR) name | |
| (10) | Data Update Request (DUR) name | |
| (11) | Title for the displayed DUR information | |
| DATE/TIME RELATION TABLE DLSID | - | |
| CETYPE | ||
| (12) | Underlines for the title | |
| (13) | Date/time of implementation for the involved DUR name | |
| (14) | Relation name for which the DUR was written | |
| (15) | Data base control table for which the DUR was written | |
| (16) | Data Load Segment (DLS) identity | |
| (17) | Control element type | see SI 210 |
| 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 | 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 :
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. |