...
- resv_begin hooks are read-only
- The type for the resv_begin event is
pbs.RESVBEGINRESV_BEGIN - RESV_BEGIN hooks run at the server
- Hooks registered to the resv_begin event will be run after the queue has been started and enabled but before email notifications and the 'B' accounting record are written.
pbs.event().accept()andpbs.event().reject()both allow the reservation to proceed. This hook is read-only.pbs.event().reject()should allow for a message to be sent to standard logging mechanisms.- Fields in the pbs.event().resv() object are the same as for the "resv_end" event.
- A rejection in the resv_begin hook will not affect the start of the reservation at this time, as the scheduler will treat the reservation as begun independent of the reservation's status in the server, provided that the reservation is otherwise runnable.
...
- resv_confirm hooks are read-only.
- The type for the resv_confirm event is
pbs.RESVCONFIRMRESV_CONFIRM. - resv_confirm hooks run at the server.
- Hooks registered to the resv_confirm event will be run immediately before the "reservation confirmed" accounting record is written in req_confirmresv().
pbs.event().accept()andpbs.event().reject()both allow the reservation to proceed. This hook is read-only.pbs.event().reject()should allow for a message to be sent to standard logging mechanisms.- Fields in the pbs.event().resv() object are the same as for the "resv_end" event.
- A rejection in the resv_confirm hook will not affect reservation confirmation at this time.
- resv_confirm hooks will be run on reservation re-confirmation.
...