Question on Association behaviour

Hi,

 

Consider the following situation below -

 

1.       You have a set of classes (parent and derived) compiled in your
user defined namespace "say" "root/xyx".

2.       Out of all those classes we consider the "DiskDrive",
"SystemDevice" and the "Realizes" classes.

a)      Parent Class for DiskDrive is "CIM_DiskDrive".

b)      My Derived class for DiskDrive : XYZ_DiskDrive -

i)                     class XYZ_DiskDrive : CIM_DiskDrive { }; 

c)       Parent Class for SystemDevice "CIM_SystemDevice".

d)      Three Derived classes on "SystemDevice" -

i)                    class XYZ_ComputerSystemVolumeSystemDevice :
CIM_SystemDevice { };

ii)                   class XYZ_ComputerSystemAlarmSystemDevice :
CIM_SystemDevice { };

iii)                 class XYZ_ComputerSystemDiskDriveSystemDevice :
CIM_SystemDevice { }; 

e)      Two Derived classes on "Realizes" -

i)                    class XYZ_DiskDrivePhysicalPackageRealizes :
CIM_Realizes { };

ii)                   class XYZ_ ComputerSystemCardRealizes :
CIM_Realizes { };

3.       Now I fire the following "associators/associatornames" i.e
"a/an" client commands to the cimserver where the above classes compiled
in the "root/xyz" namespace are present serviced by the "xyz.dll/.so"
provider - 

a)      cimcli an -n root/xyz CIM_DiskDrive -I -niq (and then I select
one of the DiskDrive objectpaths listed)

b)      cimcli a -n root/xyz CIM_DiskDrive -I -niq (and then I select
one of the DiskDrive objectpaths listed)  

 

Facts I assume:

 

1.       The result that will be obtained by the client after firing the
above commands will be :

a)      List of objectpaths of all classes associated (through any
association) with the selected diskdrive. (Objectpaths of
ComputerSystems associated with the diskdrive through
XYZ_ComputerSystemDiskDriveSystemDevice association (2/d/iii) and
Objectpaths of PhysicalPackages associated with the diskdrive through
XYZ_DiskDrivePhysicalPackageRealizes association (2/e/ii) )

 

Queries

 

1.       What will be the behavior of the CIMOM after receiving this
call -

a)      It will spawn separate and parallel "a/an" thread calls to my
provider (xyz.dll/.so), with -

i)                    Objectpath = Selected DiskDrive Path. (always)

ii)                   AssociationClass =
XYZ_ComputerSystemDiskDriveSystemDevice and
XYZ_DiskDrivePhysicalPackageRealizes only.

iii)                 ResultClass = EMPTY

iv)                 Role = EMPTY

v)                  ResultRole = EMPTY

b)      OR anything other than a), if "yes" please explain.

 

Thanks in advance.

 

Regards,

Biswapratap.

 


Please do not print this email unless it is absolutely necessary. 

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. 

www.wipro.com