HP Large Objects System Management Manual

HP Large Objects System Management Manual – 543599.001
pBuddyGroupName:
A 5 character alphanumeric name with no embedded spaces, for example:
GRP01 or B01
pCallerTransAborted:
Indicates whether the caller’s TMF transaction has been aborted
0 = not aborted
1 = aborted
3.3.2 DeleteBuddyGroup
Deletes a Buddy Group. The Buddy Group must be “inactive” before deletion is
permitted. An inactive Buddy Group is one that has no Buddy Sets.
short DeleteBuddyGroup (const char *pBuddyGroupName //
input
, short *pCallerTransAborted //
output
);
Return value:
0 = Successful
112 = Failed – Buddy Group not found
114 = Failed - Buddy Group Active
118 = Failed – Buddy Group Name is invalid
100 = System error (call GetSystemErrorString)
pBuddyGroupName:
A 5 character alphanumeric name with no embedded spaces, for example:
GRP01 or B01
pCallerTransAborted :
indicates whether the caller’s TMF transaction has been aborted
0 = not aborted
1 = aborted
3.3.3 CreateBuddySet
Creates a BuddySet and its associated BuddySpaces. The API uses the entries in the
parm table for this BuddyGroup to determine the size and shape of the storage. The
buddy space file extents are fully allocated and the finite state machine (FSM) is
initialized to all zeroes. This can take some time if there are many large buddy spaces
in the set.
CreateBuddySet creates a single BuddySpace file for each segment size according to
the parameters set for the specified BuddyGroup. To allocate more storage to a
particular segment size use the CreateBuddySpace API to create additional
BuddySpace files.
Notes:
1) Using CreateBuddySet causes the file extents of all BuddySpace and FSM files to
be fully allocated. It is therefore important that sufficient disk storage space be
available on the specified volume. The amount of storage required for each BuddySet
is displayed during system initialization (see metaData.sh in the section shell scripts).
Page 15 of 37