dont allow system to start up if DBROOT 1 is not assigned to ACTIVE PARENT PM

Customer had an issue where PM1 failed and DBROOT 1 got assigned to PM2. PM2 had DBROOT 1 and 2 assigned to it and PM2 was the ACTIVE PARENT PM.. When PM1 was fixed, customer moved DBROOT 1 back to PM1, which was the incorrect process to do. DBROOT 2 should have been moved to PM1. The ACTIVE PARENT should always have DBROOT 1 assigned since it contains the DBRM files.
A startsystem was performed which lead to the deletion of the DBRM files because of the incorrect assignment.

The startsystem needs to check that DBROOT 1 is correctly assigned before allow a startsystem to run.