HP Large Objects System Management Manual

HP Large Objects System Management Manual – 543599.001
2) The BuddySet subvolume name is automatically derived from data held in the
Large Object SQL DB. The name is formulated as follows:
ssssxxnn
Where,
ssss is the ObjectStoreNumber (as set in the .profile shell script)
xx is an alpha pair automatically associated with the BuddyGroup.
nn is a sequential number allocated when each BuddySet is created.
Examples of subvolume names are: LS01AA01, LS01AA02 and LS01AB01,
LS01AB02 and so on.
short CreateBuddySet (const char *pBuddyGroupName // input
, const char *pVolumeName // input
, short *pCallerTransAborted // output
);
Return value:
0 = Successful
112 = Failed – Buddy Group not found
130 = Failed – Insufficient Disk space available to create FSM/Buddy Space
files
131 = Failed – Volume/Subvolume doesn’t exist
134 = Failed – Number of FSMs and Buddy Spaces exceeds the limit on
opens
100 = System error (call GetSystemErrorString)
pBuddyGroupName:
A 5 character alphanumeric name with no embedded spaces, for example:
GRP01 or B01.
pBuddyVolume:
An 8 character volume name (including “$”) upon which the Buddy Set is
created. The volume must be audited and have sufficient available space to
create FSM and Buddy Space files as configured by Parameter values.
pCallerTransAborted :
Indicates whether the caller’s TMF transaction has been aborted
0 = not aborted
1 = aborted
3.3.4 DeleteBuddySet
Deletes an entire BuddySet and its associated BuddySpaces provided the BuddySet
contains no objects and no processes have the BuddySpace or FSM files open.
Note: any additional BuddySpaces created using the CreateBuddySpace API, are also
deleted when DeleteBuddySet is successfully invoked.
short DeleteBuddySet (const char *pBuddyGroupName // input
, const char *pBuddyVolume // input
, const char *pBuddySubvolume // input
, short *pCallerTransAborted // output
);
Page 16 of 37