search cancel

An Online Reorg, FFOR, fails indicating that the Reorg has been abandoned due to an unrecoverable error.

book

Article ID: 42576

calendar_today

Updated On:

Products

Database Analyzer (IMS Tools) Mainframe Configuration Manager for IMS for z/OS IMS TOOLS - MISC Compress Data Compression (IMS Tools) Database Analyzer for IMS for z/OS Database Copier for IMS for z/OS Database Organizer for IMS for z/OS Mainframe Extended Terminal Manager (IMS Tools) High Performance Recovery for IMS for z/OS Database Organizer (IMS Tools) Mainframe Program Restart Manager for IMS for z/OS Secondary Index Builder for IMS for z/OS Secondary Index for IMS for z/OS

Issue/Introduction

Symptom:

An Online Reorg of a database in an IMSplex data-sharing environment has failed with the following errors:

HPO0053E IMS SYSTEM sys2     IS NOW SHARING dbname
HPO0054E REORG ABANDONED DUE TO PRECEDING ERROR
HPO0507E REORG ABANDONED DUE TO THE DETECTION OF AN UNRECOVERABLE ERROR
HPO1D01I ORIGINAL DATABASE SUCCESSFULLY REINSTATED 

This corresponds to the following messages in the ITK STC log:

SET ERROR   sys1     dbname   HPOFROG0
HPOFROG0: INTERLOPER DETECTED

 

Workaround:

Database Organizer has detected an interloper.

Initially nothing is shared, as confirmed by the HPO5207I message.

HPO5207I DATABASE IS NOT SHARED

Then a new player (sys2) comes in afterwards as indicated by the HPO0053E message:

HPO0053E IMS SYSTEM sys2 IS NOW SHARING dbname

This is a valid error message.

To avoid this type of failure the recommendation is to make sure that an FFOR doesn’t begin on a database, until any system that may use it, already has it opened (not just /STARTed). This is something that we usually only see on test-systems where everything gets cleaned up/restarted more often, not on a production system where the databases would be open (therefore used/shared) pretty much all the time.             

Environment

Release:
Component: DBO