HPO5207I DATABASE IS NOT SHARED HPO0545E THE INTEGRITY SUBTASK DETECTED A DATABASE INTERLOPER

Products

• High Performance Recovery for IMS for z/OS
• DATABASE MANAGEMENT SOLUTIONS FOR IMS FOR Z/OS

Issue/Introduction

During Full Function Online Reorg (FFOR) of a database receiving message:

HPO5207I DATABASE IS NOT SHARED

...

HPO0545E THE INTEGRITY SUBTASK DETECTED A DATABASE INTERLOPER
HPO0507E REORG ABANDONED DUE TO THE DETECTION OF AN UNRECOVERABLE ERROR
HPO1D01I ORIGINAL DATABASE SUCCESSFULLY REINSTATED

How to prevent interloper conditions?

Resolution

When FFOR starts up it builds an inventory of sharing subsystems against the database to be reorganized by reading active sub system records from the DBRC recon.

Message HPO5209I and HPO5210I displays the sub systems identified at that time, for example:
HPO5209I DATABASE IS BEING USED BY THE FOLLOWING SUBSYSTEMS   
HPO5210I SUBSYSA     SUBSYSB     

 

Manual Identification of subsystems:                    

The DBRC LIST.SUBSYS ALL  command displays ALL active subsystem allocations belonging to a database, for example:

SSID=IMSD      LOG START=2016.202 20:25:51.101205 +00:00
COEXISTENCE LEVEL=14.1              
AUTHORIZED DATA BASES/AREAS=2      VERSION=13.1  XRF CAPABLE=NO   
                                                   ENCODED
   -DBD-        -AREA-   -LEVEL-  -ACCESS INTENT-  -STATE-
   D11          **NULL**    3        UPDATE           3
   D110         **NULL**    3        UPDATE           3 

The LIST.DB DBD command display all owning subsystems of a database, for example:

DBD=D11                      IRLMID=*NULL        DMB#=2146    TYPE=IMS
SHARE LEVEL=3               GSGNAME=**NULL**     USID=0000000012
ASSOCIATED SUBSYSTEM INFORMATION:
                             ENCODED  B/O NEEDED
   -SSID-   -ACCESS INTENT-  -STATE-   -COUNT-  -SS ROLE-
  SUBSYSA         UPDATE           3         0      ACTIVE
  SUBSYSB         UPDATE           3         0      ACTIVE  

 

Database association to a sub system:

When a transaction or BMP is scheduled against a database for the first time, the IMS subsystem name is registered in DBRC against databases
being processed by the application PSB. The /STA DB OPEN command will also create a sub system record in DBRC to establish ownership
between the subsystem and the database. The subsystem record remain active against the database until a /DBR is received.
Therefore, when FFOR is scheduled, subsystem entries  created by application processing or a /STA DB OPEN command is used to identify
IMS systems processing against a database via messages HPO5209I and HPO5210I.

How to prevent interloper conditions:

The most general way would be to issue a /STA DB OPEN on each IMS system BEFORE the FFOR cycle.
The LIST.DB DBD command displays allocated subsystems against the database.

In the example below, SUBSYSA and SUBSYSB is sharing database D11

The LIST.DB DBD command display all owning subsystems of a database, for example:

DBD=D11                      IRLMID=*NULL        DMB#=2146    TYPE=IMS 
SHARE LEVEL=3               GSGNAME=**NULL**     USID=0000000012
ASSOCIATED SUBSYSTEM INFORMATION:
                             ENCODED  B/O NEEDED
   -SSID-   -ACCESS INTENT-  -STATE-   -COUNT-  -SS ROLE-
  SUBSYSA         UPDATE           3         0      ACTIVE
  SUBSYSB         UPDATE           3         0      ACTIVE