RRN 01546 DUR MANAGEMENT: IMPLEMENT

MJWBWH05

Message Triggering Condition

Response in case of either successful, successful with warning or not successful result of the execution, on operator request to implement the Data Update Request(s) using the option IMPLMENT, via the ollowing MMC-command :
CRN 07678 MANAGE-DURS

Report Layout

 SWA-DB ONLINE UPDATE FAC
    (A).......................                   (B).................
                                 (C)........................... (D) (E)
    -----------------------------------------------------------------
        IMPLEMENT                                   (1) SUCCESSFUL
        ----------------------------------------------------------
        DUR (2)..... (3)................................
        TRANSID = (4)..
          (5)............ (6)..... (7).. ((8)..)  FMM ENTRY = (9)
          (10)............................... (11).
          (12)...................  (13)....
  REPORT REFERENCE NUMBER = 1546

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
(2) Data Update Request (DUR) name
(3) Update information
IMPLEMENTED BEFORE -
IMPLEMENTED IN MEMORY -
IMPLEMENTED ON DISK -
IMPLEMENTED ON DISK AND IN MEMORY -
NOT IMPLEMENTED -
(4) Transaction identity
(5) Error type see Evaluation 000000000000000000
- the parameters; (5) to (10) are
displayed in case of an error or
a warning, otherwise they are
suppressed
(6) Error location_place indicator
FOR DLS in case of INCONSISTENCY
FOR LCE in case of WARNING
IN FILE in case of GIO ERROR
IN LINE in case of SYNTAX ERROR
(7) Error location_place no
(8) Error location_place no
(9) FMM entry number location in the Disk Update
Facility (DUF) FMM where the
error has been generated
(10) Error description see Evaluation
(11) Error code
(12) Text string for kind of not found CE type
(13) Not equipped CE type

Evaluation

Key Parameter Contents / Meaning Action
1 2 3
(5) DB ERROR . . . . . . . . . . . . . . . . . . . . .
(10) BDH ERROR . . . . . . . . . . . . . . . . . . . . B
(10) DSF ERROR . . . . . . . . . . . . . . . . . . . . B
(10) DUT FAILURE . . . . . . . . . . . . . . . . . . . B
(10) GET R-CE-CLASS . . . . . . . . . . . . . . . . . . B
(10) GET R-LCESWCD1 . . . . . . . . . . . . . . . . . . B
(10) GET R-LPT-DES1 . . . . . . . . . . . . . . . . . . B
(10) GET R-RELDCR . . . . . . . . . . . . . . . . . . . B
(10) GET R-USERFILE . . . . . . . . . . . . . . . . . . B
(10) MOD R-USERFILE . . . . . . . . . . . . . . . . . . B
(5) GIO ERROR . . . . . . . . . . . . . . . . . . . .
(10) DEALLOCATE FAILURE . . . . . . . . . . . . . . . . D
(10) INVALID RECORD SIZE . . . . . . . . . . . . . . . D
(10) OPEN FAILURE . . . . . . . . . . . . . . . . . . . D
(10) READ FAILURE . . . . . . . . . . . . . . . . . . . D
(10) WRITE FAILURE . . . . . . . . . . . . . . . . . . D
(5) INCONSISTENCY . . . . . . . . . . . . . . . . . .
(10) DELETE ON FAST ACCESS REL . . . . . . . . . . . . G
(10) DELETE ON SQUEEZED REL . . . . . . . . . . . . . . G
(10) DOMAIN NOT PRESENT . . . . . . . . . . . . . . . . G
(10) ENTRY NOT PRESENT . . . . . . . . . . . . . . . . G
(10) INVALID DLS . . . . . . . . . . . . . . . . . . . G
(10) INVALID RELATION PART . . . . . . . . . . . . . . G
(10) INVALID SIZE OF DOMAIN . . . . . . . . . . . . . . G
(10) INVALID TYPE OF UPDATE . . . . . . . . . . . . . . G
(10) INVALID VERSION OF DLS . . . . . . . . . . . . . . G
(10) NO FREE TUPLE . . . . . . . . . . . . . . . . . . G
(10) NO MASTER OF REPLICATION . . . . . . . . . . . . . G
(10) NO PREPOPULATED TUPLE . . . . . . . . . . . . . . G
(10) RELATION NOT IN DLS . . . . . . . . . . . . . . . G
(10) SA NOT PRESENT IN DLS . . . . . . . . . . . . . . G
(10) STORE ON FAST ACCESS REL . . . . . . . . . . . . . G
(10) STORE ON SQUEEZED REL . . . . . . . . . . . . . . G
(10) TUPLE ALREADY STORED . . . . . . . . . . . . . . . G
(10) TUPLE NOT PRESENT . . . . . . . . . . . . . . . . G
(10) UPDATE ON VIRTUAL DOMAIN . . . . . . . . . . . . . G
(5) INPUT ERROR . . . . . . . . . . . . . . . . . . .
(10) DUR NOT FOUND . . . . . . . . . . . . . . . . . . E
(10) DUR TOO LONG . . . . . . . . . . . . . . . . . . . E
(10) GROUP INCOMPLETE : ROLLBACK TRANSID . . . . . . . E
(10) INDEX FILE EMPTY . . . . . . . . . . . . . . . . . E
(10) INPUT FILE EMPTY . . . . . . . . . . . . . . . . . E
(10) INPUT FILE TRUNCATED . . . . . . . . . . . . . . . E
(10) INVALID DUR NAME . . . . . . . . . . . . . . . . . E
(10) NOT FIRST DUR IN GROUP . . . . . . . . . . . . . . E
(10) TOO MANY DLS BLOCKS . . . . . . . . . . . . . . . E
(5) ITF ERROR . . . . . . . . . . . . . . . . . . . .
(10) FMM BDH NOT RESPONDING . . . . . . . . . . . . . . C
(10) FMM DSF NOT RESPONDING . . . . . . . . . . . . . . C
(10) FMM FDTA NOT RESPONDING . . . . . . . . . . . . . C
(10) FMM LUC NOT RESPONDING . . . . . . . . . . . . . . C
(5) SYNTAX ERROR . . . . . . . . . . . . . . . . . . .
(10) INVALID CHARACTER . . . . . . . . . . . . . . . . F
(10) INVALID DOMAIN NUMBER . . . . . . . . . . . . . . F
(10) INVALID ENTRY NUMBER . . . . . . . . . . . . . . . F
(10) INVALID KEYWORD . . . . . . . . . . . . . . . . . F
(10) INVALID TUPLE NUMBER . . . . . . . . . . . . . . . F
(10) INVALID VALUE . . . . . . . . . . . . . . . . . . F
(10) KEYWORD NOT ALLOWED . . . . . . . . . . . . . . . F
(10) VALUE MISSING . . . . . . . . . . . . . . . . . . F
(5) WARNING . . . . . . . . . . . . . . . . . . . . .
(10) INDEX FILE FULL . . . . . . . . . . . . . . . . . A
(10) MEMORY NOT UPDATED : CE DOWN . . . . . . . . . . . A
(10) MEMORY NOT UPDATED : MUFF CODE . . . . . . . . . . A
(10) MEMORY NOT UPDATED : OVERLOAD . . . . . . . . . . A
(10) MEMORY NOT UPDATED : RESTART . . . . . . . . . . . A
(10) MEMORY NOT UPDATED : TIMEOUT . . . . . . . . . . . A
(10) NO UPDATES DONE . . . . . . . . . . . . . . . . . A

Action Description

Action Meaning
A The DUR has at least been implemented on disk. Taking into account the given warning and the input value for the 'MEMUPD' parameter, the DUR is implemented in the memory or not.

The possible warning cases are described below :

  • INDEX FILE FULL

In case the actual index file has been filled up, this warning is reported, the DUF FMM switches over to the second file and overwrites the previously stored information.

<addition_DLS_info (parameter 7)> not displayed,

<addition_info (parameter 10)> displayed: file identity of the index file (decimal file identity)

  • MEMORY NOT UPDATED : MUFF CODE

The memory copy has not been updated although the parameter 'MEMUPD' was set to true. Reason: error occured during memory update in the MUF FMM or R_MUFFPROC. In case the related physical processor identity in the relation R_CE_CLASS is set to FFFFH the DUF FMM won't send a memory update request and does not report the described warning to the operator terminal.

<addition_DLS_info (parameter 6,7)> displayed: 'FOR LCE' decimal lce identity,

<addition_info (parameter 10)> displayed: return code received from the MUF FMM.

A list of possible return codes (decimal values) is shown below :

RETURN CODE MEANING =========== ======= 0 ...... SUCCESSFULL 1 ...... CHANGE BLOCK SIZE = 0 2 ...... CHANGE OFFSET OUT OF RANGE 3 ...... INDEX INVALID 4 ...... INDEX OUT OF USED RANGE 5 ...... STACK DATA INCONSISTENT 6 ...... SEG INDICATOR INCONSISTENT 7 ...... COMMAND INVALID 9 ...... DLS DATA INCONSISTENT 10 ...... DLS RANGE CHECK FAILED 11 ...... REL NOT FOUND IN LDIR 12 ...... RELPART NOT FOUND IN LDIR 13 ...... REL NOT FOUND IN GDIR 14 ...... NO DISK ONLY AREA 15 ...... SPEC HOLD NOT SET

  • MEMORY NOT UPDATED : CE DOWN

The memory copy has not been updated although the parameter 'MEMUPD' was set to true. Reason: destination processor is not running

<addition_DLS_info (parameter 6,7)> displayed: 'FOR LCE' decimal lce identity,

<addition_info (parameter 10)> not displayed.

  • MEMORY NOT UPDATED : OVERLOAD

The memory copy has not been updated although the parameter 'MEMUPD' was set to true. Reason: destination processor is in overload

<addition_DLS_info (parameter 6,7)> displayed: 'FOR LCE' decimal lce identity,

<addition_info (parameter 10)> not displayed.

  • MEMORY NOT UPDATED : RESTART

The memory copy has not been updated although the parameter 'MEMUPD' was set to true. Reason: destination processor is restarted

<addition_DLS_info (parameter 6,7)> displayed: 'FOR LCE' decimal lce identity,

<addition_info (parameter 10)> not displayed.

  • MEMORY NOT UPDATED : TIMEOUT

The memory copy has not been updated although the parameter 'MEMUPD' was set to true. Reason: time out is received during memory update.

<addition_info (parameter 10)> not displayed.

  • NO UPDATES DONE

No action was taken: Tuple(s) to be removed is (are) already deleted; None of the stored tuples match the given qualification conditions.

<addition_DLS_info (parameter 7)> not displayed.

<addition_info (parameter 10)> not displayed.

B No DUR implementation is done.

<DUR name (parameter 2)> the DUR name to be implemented. (May be filled up with blanks if the error occured before the real DUR implementation handling started.)

<FMM location (parameter 8)> this is a decimal value indicating the location in the DUF FMM where the error has been generated.

<error description (parameter 9)> it can ave one of the following meanings :

  • BDH ERROR <addition_info (parameter 10)> displayed: <upd_resp_sub_status>.
  • DSF ERROR <addition_info (parameter 10)> displayed: <dsf_return_code>.
  • DUT FAILURE <addition_info (parameter 10)> not displayed. <db_status>
  • GET R_CE_CLASS <addition_info (parameter 10)> displayed: <db_status>
  • GET R_LCESWCD1 <addition_info (parameter 10)> displayed: <db_status>
  • GET R_LPT_DES <addition_info (parameter 10)> displayed: R_LPT_DES1/R_LPT_DES2 <db_status>
  • GET R_RELDCR <addition_info (parameter 10)> displayed: <db_status>
  • GET R_USERFILE <addition_info (parameter 10)> displayed: <db_status>
  • MOD R_USERFILE <addition_info (parameter 10)> displayed: <db_status>

<upd_resp_sub_status> BDH update response sub status.

A list of possible subcodes is given below :

SUB CODE MEANING ======== ======= 0 ... UPD_SUB_SUCCESSFUL 1 ... GET_BUFFER_NOK 2 ... JOB_FOR_STORE_RES_NOT_FOUND 3 ... SF_UPDATE_TRA_FAILS 4 ... SF_UPDATE_TRA_FAIL_NRB_NRF_RUN 5 ... SF_UPDATE_EOT_FAILS 6 ... MEMORY_DISK_DISCREPANCY 7 ... JOB_FOR_CPL_OPEN_NOT_FOUND 8 ... WRONG_IOS_CPL_IN_CPL_OPEN 9 ... TIME_OUT_IN_CPL_OPEN 10 ... JOB_FOR_CPL_PUT_NOT_FOUND 11 ... WRONG_IOS_CPL_IN_CPL_PUT 12 ... TIME_OUT_IN_CPL_PUT 13 ... JOB_FOR_TIMER_EX_NOT_FOUND 14 ... JOB_FOR_CPL_WRITE_NOT_FOUND 15 ... WRONG_IOS_CPL_IN_CPL_WRITE 16 ... JOB_FOR_CPL_GET_NOT_FOUND 17 ... WRONG_IOS_CPL_IN_CPL_GET 18 ... TIME_OUT_IN_CPL_GET 19 ... WRONG_INTERNAL_TRANSACTION_ID 20 ... JOB_QUEUE_FULL 21 ... SNG_QUEUE_FULL 22 ... RUNNING_TIME_EXPIRED 23 ... INTERNAL_TRA_QUEUE_FULL 24 ... TRANSACTION_QUEUE_FULL 25 ... WRONG_IOS_CPL_IN_CPL_CLOSE 26 ... JOB_FOR_CPL_CLOSE_NOT_FOUND 27 ... WRONG_IOS_CPL_IN_CPL_READ 28 ... JOB_FOR_CPL_READ_NOT_FOUND 29 ... SF_UPDTRA_FAIL_RESTART_PRB_RUN 30 ... WRONG_SEC_LEV_AND_OR_REC_TYP 31 ... WRONG_SEC_AND_OR_REC_IN_TRA 32 ... SFH_IS_CHECKING_ITS_FILES 33 ... REL_BLOCKED_BY_EXTENSION 34 ... NO_EXT_CHECK_DB_ERROR 35 ... PROCESS_ID_WRONG 36 ... REL_BLOCKED_BY_DBOC 37 ... LLI_TUPLE_LOCKED_BY_OTHER_TRAN 38 ... LLI_RELATION_LOCKED_BY_OTHER_T 39 ... LLI_TUPLE_LOCKED_BY_SINGLE_OR 40 ... LLI_RELATION_LOCKED_BY_SINGLE 41 ... LLI_LOCK_NOT_FOUND 42 ... LLI_LOCK_TABLE_FULL 44 ... REMOTE_LOCK_NOT_ALLOWED 45 ... REM_CE_OVERLOAD 46 ... REM_CE_RESTART 47 ... WRONG_SEG_INDIC 48 ... RESTART_RUNNING_TIME_EXPIRED 49 ... RESTART_SNG_QUEUE_FULL 50 ... RESTART_UPD_FAILS 51 ... RESTART_NO_OPEN_TRA 52 ... RESTART_PRB_RUN 53 ... PRB_ALL_UPD_FAILES 54 ... RESTART_WRONG_INTERNAL_TRANSAC 55 ... GDIR_ACCESS_FAILED

<dsf_return_code> DSF return code.

A list of possible return codes is given below :

RETURN CODE ................ MEANING ============================ ======= 0....ERR_RESET 1....ERR_INP_DLS_ID ...... Not found DLS id. 2....ERR_INP_FILE ........ File id not found. 3....ERR_INP_PLCE ........ Access to DLSHD failed. 4....ERR_50_BYTES ........ Error during read of 50 first meaningfull DLS bytes. 5....ERR_GDIR ............ Access to R_GDIR_V4 in PLCE fail. 6....ERR_LCESWCD1 ........ Access to R_LCESWCD1 failed. 7....ERR_WRONG_REL_TYPE2 . No info for relation in requested DLS 8....ERR_WRONG_REL_TYPE .. Relation indicated as error in requested DLS. 9....ERR_FETCH_GDIR ...... GDIR tuple for relelation not found. 10....ERR_FAST_PTR_FIRST .. R_FAST_PTR not found in GDIR. 11....ERR_REMOVE_BLOCK..... Error received from BDH while remove of blokking. 12....ERR_SET_BLOCK........ Error received from BDH while setting of blokking. 13....ERR_NOT_FOUND_ADDR .. Address not found in CI's. 14....ERR_2_NOT_FOUND_ADDR..Address not found in CI's. 15....ERR_DLS_IDX ......... Get on R_DLS_IDX failed. 16....ERR_WRONG_RELATION_PART Wrong relation part specified. 17....ERR_WRONG_REC_DO .... Wrong record for Disk Only specified. 18....ERR_UNKNOWN_ACTION .. Action parameter not recognized. 19....ERR_RELDCR .......... Access on R_RELDCR failed. 25....ERR_IO_GET_FAILED 34....ERR_FAST_PTR_SEC 41....ERR_NF_PST_ENTRY 100....ERR_TIMEOUT_GET ..... Timeout on i/o get request 101....ERR_IO_OPEN_READ .... Error on i/o open request 102....ERR_IO_OPEN_TO ...... Timeout on i/o open request 103....ERR_IO_GET .......... Error on i/o get request 104....ERR_IO_GET_TO ....... Timeout on i/o get request

<db_status> Data base return code (see SI 057).

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 No DUR implementation is done.

<DUR name (parameter 2)> the DUR name to be implemented. (May be filled up with blanks if the error occured before the real DUR implementation handling started.)

<FMM location (parameter 8)> this is a decimal value indicating the location in the DUF FMM where the error has been generated.

<error description (parameter 9)> it can have one of the following meanings :

  • FMM BDH NOT RESPONDING
  • FMM DSF NOT RESPONDING
  • FMM FDTA NOT RESPONDING
  • FMM LUC NOT RESPONDING

Repeat the command after some time. If the result is still unsuccessful, special fault clearing will be necessary.

In case that the special fault clearing is necessary, see fault reporting procedures. Refer to the document FAULT REPORTING PROCEDURES which is part of the Customer Documentation Guide.

D No DUR implementation is done.

<DUR name (parameter 2)> the DUR name to be implemented. (May be filled up with blanks if the error occured before the real DUR implementation handling started.)

<file (parameter 7)> this is the logical file identity (decimal) where the error occurred.

<FMM location (parameter 8)> this is a decimal value indicating the location in the DUF FMM where the error has been generated.

<error description (parameter 9)> it can have one of the following meanings :

  • INVALID RECORD SIZE <addition_info (parameter 10)> displayed: record size.
  • OPEN FAILURE <addition_info (parameter 10)> displayed: <I/O sub code>.
  • READ FAILURE <addition_info (parameter 10)> displayed: <I/O sub code>.
  • WRITE FAILURE <addition_info (parameter 10)> displayed: <I/O sub code>.
  • DEALLOCATE FAILURE <addition_info (parameter 10)> not displayed.

<I/O sub code>: see SI 058 for a full description of I/O sub codes.

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

E No DUR implementation is done.

<DUR name (parameter 2)> the DUR name to be implemented. (May be filled up with blanks if the error occured before the real DUR implementation handling started.)

<FMM location (parameter 8)> this is a decimal value indicating the location in the DUF FMM where the error has been generated.

<error description (parameter 9)> error description can have different meanings, dependent on the particular error that has been detected. These are described as follows :

  • DUR NOT FOUND

The DUR name entered in the MMC-command is different from the DUR name found in the input file.

<addition_info (parameter 10)> not displayed.

  • DUR TOO LONG

The total number of characters entered in the actually treated or the following DUR is >62K or the expansion in the workfile becomes too big. Split the dur in smaller parts.

<addition_info (parameter 10)> not displayed.

  • INDEX FILE EMPTY

The parameter 'NEXT' or 'CONTINUE' entered in the MMC-command is invalid. Reason: the index file is empty.

<addition_info (parameter 10)> displayed: file identity of the index file (decimal file identity)

  • INPUT FILE EMPTY

No DUR found in the input file.

<addition_info (parameter 10)> displayed: file identity of the input file (decimal file identity).

  • INPUT FILE TRUNCATED

Input file corrupted. Reason: transfer of input file by DUFFIX PC TOOL not successfully completed.

<addition_info (parameter 10)> displayed: file identity of the input file (decimal file identity).

  • INVALID DUR NAME

DUR name in the input file is incorrect. See the Restrictions part of the MMC-command.

  • NOT FIRST DUR IN GROUP

The implemantation request for a DUR GROUP must always be accompanied with the DUR name of the first DUR within the group and must include all DURs of the group.

<addition_info (parameter 10)> not displayed.

  • GROUP INCOMPLETE : ROLLBACK TRANSID

This error is also reported in case inconsistencies are detected between the given input parameter values and the contents of the DUR group.

<addition_info (parameter 10)> displayed: transaction identity of the DUT in which the DUR implementation failed (decimal transaction identity).

  • TOO MANY DLS BLOCKS

A DUR-GROUP contains more than 195 DLS and/or DLS RANGE description blocks. (Restriction of current implementation.)

<addition_info (parameter 10)> not displayed.

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 and it is quite possible that special fault clearing will be necessary.

F No DUR implementation is done.

<DUR name (parameter 2)> the DUR name to be implemented. (May be filled up with blanks if the error occured before the real DUR implementation handling started.)

<location (parameter 7)> decimal DUR line number where the error has been detected.

<fmm location (parameter 8)> this is a decimal value indicating the location in the DUF FMM where the error has been generated.

<error description (parameter 9)> the possible error cases are shown below :

  • INVALID CHARACTER
  • INVALID DOMAIN NUMBER
  • INVALID ENTRY NUMBER
  • INVALID KEYWORD
  • INVALID TUPLE NUMBER
  • INVALID VALUE
  • KEYWORD NOT ALLOWED
  • VALUE MISSING

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

G No DUR implementation is done.

<DUR name (parameter 2)> the DUR name to be implemented. (May be filled up with blanks if the error occured before the real DUR implementation handling started.)

<FMM location (parameter 8)> this is a decimal value indicating the location in the DUF FMM where the error has been generated.

<error description (parameter 9)> error description can have different meanings, dependent on the particular error that has been detected. These are described as follows :

  • STORE ON FAST-ACCESS REL

Create-tuple command not allowed for FAST ACCESS RELATIONS; only MODIFY or MODIFY ALL is allowed.

<addition_DLS_info (parameter 7)> not displayed.

<addition_info (parameter 10)> not displayed.

  • DELETE ON FAST-ACCESS REL

Delete-tuple command not allowed for FAST ACCESS RELATIONS; only MODIFY or MODIFY ALL is allowed.

<addition_DLS_info (parameter 7)> not displayed.

<addition_info (parameter 10)> not displayed.

  • STORE ON SQUEEZED REL

Create-tuple command not allowed on SQUEEZED RELATIONS.

<addition_DLS_info (parameter 7)> not displayed.

<addition_info (parameter 10)> not displayed.

  • DELETE ON SQUEEZED REL

Delete-tuple command not allowed on SQUEEZED RELATIONS.

<addition_DLS_info (parameter 7)> not displayed.

<addition_info (parameter 10)> not displayed.

  • DOMAIN NOT PRESENT

Domain identity does not exist.

<addition_DLS_info (parameter 7)> not displayed.

<addition_info (parameter 10)> displayed: domain number (decimal value).

  • ENTRY NOT PRESENT

Entry number does not exist.

<addition_DLS_info (parameter 7)> not displayed.

<addition_info (parameter 10)> displayed: entry number (decimal value).

  • INVALID DLS

DLS identity does not exist.

<addition_DLS_info (parameter 7)> not displayed.

<addition_info (parameter 10)> displayed: DLS identity (decimal value).

  • INVALID VERSION OF DLS

Mismatch between the given DLS VERSION and the current DLS VERSION stored in R_DLSHD_V4. In case the DLS version is not specified within the DUR, then the DUF FMM will retrieve the current DLS version out of the relation R_DLSINDEX.

<addition_DLS_info (parameter 7)> not displayed.

<addition_info (parameter 10)> displayed: DLS identity (decimal value).

  • INVALID SIZE OF DOMAIN

The number of bytes which have been entered for the domain to be modified is wrong.

<addition_DLS_info (parameter 7)> not displayed.

<addition_info (parameter 10)> displayed: domain number (decimal value).

  • INVALID RELATION PART

Wrong relation part number entered.

<addition_DLS_info (parameter 7)> displayed: 'FOR DLS' decimal dls identity.

<addition_info (parameter 10)> not displayed.

  • INVALID TYPE OF UPDATE

Wrong type of update entered.

<addition_DLS_info (parameter 7)> not displayed.

<addition_info (parameter 10)> not displayed.

  • NO MASTER OF REPLICATION

The DLS or DLS RANGE description block does not contain the DLS of the master processor for this replicated relation.

<addition_DLS_info (parameter 7)> not displayed.

<addition_info (parameter 10)> not displayed.

  • RELATION NOT IN DLS

No entry for the given relation has been found in the relation R_GDIR_V4 for the given DLS. Either the relation name or the DLS/ DLS RANGE description block is wrong.

<addition_DLS_info (parameter 7)> not displayed.

<addition_info (parameter 10)> displayed: DLS identity (decimal value).

  • SA NOT PRESENT IN DLS

No secondary area present.

<addition_DLS_info (parameter 7)> not displayed.

<addition_info (parameter 10)> displayed: DLS identity (decimal value).

  • NO FREE TUPLE

No space available for storage.

<addition_DLS_info (parameter 7)> displayed: 'FOR DLS' decimal dls identity.

<addition_info (parameter 10)> not displayed.

  • TUPLE ALREADY STORED

An attempt was made to store a tuple which has already been stored.

<addition_DLS_info (parameter 7)> displayed: 'FOR DLS' decimal dls identity.

<addition_info (parameter 10)> displayed: tuple number (decimal value).

  • TUPLE NOT PRESENT

Tuple number out of range / Modify on non existing tuple of a non fast access relation.

<addition_DLS_info (parameter 7)> displayed: 'FOR DLS' decimal dls identity.

<addition_info (parameter 10)> displayed: tuple number (decimal value).

  • UPDATE ON VIRTUAL DOMAIN

An update on a virtual domain is not allowed.

<addition_DLS_info (parameter 7)> not displayed.

<addition_info (parameter 10)> displayed: domain number (decimal value).

  • NO PREPOPULATED TUPLE

For squeezed relations of type_1, the disk copy does not contain any prepopulated tuple.

<addition_DLS_info (parameter 7)> not displayed.

<addition_info (parameter 10)> not displayed.

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