Did you receive the error while,  doing a DBGET, or DBPUT, DBDELETE?

  If it was a DBGET, you should also verify that you have an good
database/set/item locking scheme in place (this includes locking before
calling DBGET).  It is very possible to get broken chain errors while
using a DBGET if entries on the same chain are deleted with DBDELETE.

If are locking before calling DBGET or the problem occurs on DBDELETE or
DBPUT, then you should also use ADAGER to check the masters that connect
to the detail set as well as the detail set itself.

"Pandey, Pushkar TCS1C" wrote:
>
> Gents,
>
> Can you please let me know how to solve the problem.
>
> **********************************
> EPMARS - BROKEN BACKWARD CHAIN
> Please rectify the BROKEN BACKWARD CHAIN:SET 97 PATH 9 in EPMARS.
> See the following Terolog file error message.
> TURBOIMAGE RESULT; RETURN STATUS = 18
> IMAGE CALL INFORMATION NOT AVAILABLE
> BROKEN BACKWARD CHAIN: SET 97 PATH 9 ENTRY 0 0 HEX DUMP OF STATUS ARRAY
> FOLLOWS:0012 0061 0000 0000 0001 0009 4163 819e 0000 0e77
> ********************************************
>
> The chain in the database had been broken.
>
> If I run the Fix chain of the adager utility is it ok
>
> Please pass your experience  on this regard at the earliest
>
> Regards
> Pushkar Pandey
> Sultanate of Oman