HCL Notes and Domino 9.0 Social Edition Forum

Jun 18, 2017, 10:56 PM

34 Posts

Need more details (and some thoughts & suggestions)

I assume when you say " using Lotus api to create meeting" that you mean you used core APIs like NSFNoteCreate() and NSFSetItemText() (or the LotusScript equivalents) to create a doc that looks like a booked room reservation. If not then please provide some more details about what kind of docs you are creating from your code.

R&R booking is not done by simply creating a "booked" reservation for a room in the R&R database. ONLY the Rooms & Resource Manager (RnRMgr) task can do that. RnRMgr is designed to be avoid double bookings which can happen under the pre-R7.0 architecture. It does this by being the final approver for a request. Anyone who simply creates what looks like a meeting reservation will find they never get the room they want because RnRMgr did not see and approve a request.

Your tool / code needs to create a reservation request in the R&R dB which looks like a reservation request that comes from a users Calendar. You can create and save it in the R&R dB; Domino will notify RnRMgr of your request and RnRMgr will pick it up and either approve, decline or defer it (e.g. wait for a room owner to approve it).

If you set DEBUG_RNRMGR=31 you can see when RnRMgr picks up and processes requests. If you create a reservation, it does not see it because it is not a request. You will not see RnRMgr do anything with your reservation either because it is not properly formed (e.g. missing some items) or because it is not a request. There will be console messages that tell you more details when you set DEBUG_RNRMGR.

If the problem is you create room requests, not reservations, but your requests do not get processed then the issue is likely with the items (or lack of expected items). The core autoprocessing code that RnRMgr uses has its own INIs to set to give more information on any failures that happen:

CSLogAutoprocess=1
CSReportErrors=1
DEBUG_CS_LEVEL=11

All of the INIs are dynamically checked so you do not need to restart any tasks once you set them. Once set they will show you what the system does not like about your requests (if you are creating them). As I said earlier, make sure you are creating requests for rooms, not actual booked reservations (e.g. $BusyName = "My Room/Acme", $BusyPriority="2", etc).

Bruce
IBM

By Role

Busytime.nsf not updated