3(2005-06-09)
π NAME π
CMCIClientFT.referenceNames() β bestie, this one enumerates the association ObjectPaths for a class instance. It's giving "who's associated with me" energy. π¦
β¨ SYNOPSIS β¨
#include <cmci.h>
CMPIEnumeration*
CMCIClientFT.referenceNames(CMCIClient*cl,
CMPIObjectPath*op,
constchar*resultClass,
constchar*role,
CMPIStatus*rc);
πΈ DESCRIPTION πΈ
Okay so what this does: it enumerates association instances that refer to the Instance defined by the op reference. That's the whole vibe. π«Ά
Now let's meet the arguments, because there are five of them and they all matter:
clβ the client object pointer. Just your client, being a client. πopβ an ObjectPath object pointer holding the reference that contains the namespace and classname components. This is the Instance everyone's about to be associated with.resultClassβ if it's notNULL, this is a valid class name used to filter the returned set of association objects. How? By eliminating objects that aren't an Instance of this Class or one of its subclasses. No cap, it prunes the whole friend group. βοΈroleβ if it's notNULL, this is a valid property name used to filter the returned set of instance objects. It eliminates objects that aren't associated to the source object by an association where the source object plays the specified role. Translating that: the name of the property in the association class that refers to the source object has to match the value of this parameter. iykyk. πrcβ returns the operation status. It gets suppressed whenNULL, so if you don't care, don't pass it. π
π RETURN VALUE π
When it's successful, CMCIClientFT.referenceNames() returns a pointer to a CMPIEnumeration object that contains the class association reference objects found that match the association criteria, and it sets a successful operation status code in rc. Slay. β¨
When it's unsuccessful, it returns a NULL pointer and sets the operation status error code and corresponding error string in rc. Sad girl hours, but at least rc tells you why. π
π ERRORS π
Nothing listed here in the original, bestie. This section is literally just vibes and empty space. π³οΈ
π EXAMPLES π
Also empty! No examples were provided, so I'm not gonna invent one and lie to you. Periodt. π«
π§ CONFORMING TO π§
Yep, this one's blank too. No conformance claims on the page, so we're not making any up. π
π₯ SEE ALSO π₯
- Common Manageability Programming Interface (CMPI) - OpenGroup
CMCIClient(3)CMPIEnumeration(3)CMPIObjectPath(3)CMPIStatus(3)
and that's the whole page, no notes πβ¨
this lil manual page lives in section 3 and is dated 2005-06-09 β yes, it's an elder but it still ate. It came to you courtesy of the SFCBroker Client Library, version sfcc. ππ
π¦ where this page comes from
- centos-stream 10: sblim-sfcc 2.2.8-28.el10 Β· EPL-1.0
- centos-stream 9: sblim-sfcc 2.2.8-18.el9 Β· EPL-1.0
- centos-stream 9: sblim-sfcc 2.2.8-18.el9 Β· EPL-1.0
- fedora 43: sblim-sfcc 2.2.8-29.fc43 Β· EPL-1.0
- fedora 43: sblim-sfcc 2.2.8-29.fc43 Β· EPL-1.0
- fedora 44: sblim-sfcc 2.2.8-30.fc44 Β· EPL-1.0
- fedora 44: sblim-sfcc 2.2.8-30.fc44 Β· EPL-1.0
- nixos 26.05: sblim-sfcc 2.2.8-unstable-2023-06-26
- nixpkgs unstable: sblim-sfcc 2.2.8-unstable-2023-06-26
- opensuse-leap 16.0: sblim-sfcc-devel 2.2.9~rc1-bp160.1.13 Β· EPL-1.0
- opensuse-leap 16.0: sblim-sfcc-devel 2.2.9~rc1-bp160.1.13 Β· EPL-1.0
- opensuse-leap 16.0: sblim-sfcc-devel 2.2.9~rc1-bp160.1.13 Β· EPL-1.0
- opensuse-leap 16.0: sblim-sfcc-devel 2.2.9~rc1-bp160.1.13 Β· EPL-1.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms