/*============================================================================= Copyright (c) 2005 UGS Unpublished - All rights reserved THIS PROGRAM IS AN UNPUBLISHED WORK FULLY PROTECTED BY THE UNITED STATES COPYRIGHT LAWS AND IS CONSIDERED A TRADE SECRET BELONGING TO THE COPYRIGHT HOLDER. ==============================================================================*/ /** @file This file contains site reservation ITK interfaces */ /* */ /** @defgroup GMS_RES Global Multi Site Reservation The GMS reservation (GMS_RES) ITK functions provide site check-out, site check-in, site cancel check-out, functionality. This uses the same mechanism that the RES module uses.i.e An ImanReservation object is associated with each checked out object via an IMAN_RES_checkout GRM relation. This reservation functionality gives the capability to reserve objects for other sites to modification. Not all objects can be site checked out. The following classes and their sub-classes are valid for check-out:
Attribute | Description |
Site Reserved | A logical to differentiate the site check out from remote check out. |
Remote site | Tag of the site to which the object is checked out. |
Reservation Type | Integer that indicates whether check-out is with or without export. This attribute has RES_EXCLUSIVE_RESERVE for site checkout. |
User | Tag to the user that currently holds the associated object's check-out. It can be a NULLTAG in case of replica |
Group object | Tag of the group objectof the user who site checked out the object. It can be a NULLTAG in case of replica |
Reservation State | Integer that holds ImanReservation object current check-out state. This attribute has #RES_RESERVE |
Notification List | VLA containing the tags of users that wish to be notified when the associated object's check-out status changes. |
Date | A date_t that holds the date of the current check-out. |