Hello,
Would like to ask you - do you have any idea how to fix/workaround this issue with "Rooms and Resources. Awaiting all clustermates initialization before resuming autoprocessing.
technote:
http://www-01.ibm.com/support/docview.wss?uid=swg21249765&myns=swglotus&mynp=OCSSKTMJ&mync=R
Subject: Why?
If the clustermate is down, RnRMgr cannot know if there are requests on that cluster copy of the database, therefore it can cause double bookings to occur. By design, RnRMgr waits for all clustermates to come back up so it can CHECK them for queued requests. This only occurs from a cold start of the server.
For more on clustering Resource Reservations systems, please see this wiki article: