RE: How to use __MethodParameters in CIM_InstMethodCall

 

 

From: [email protected]
[mailto:[email protected]] 
Sent: Friday, May 21, 2010 2:25 AM
To: Ericson, George; [email protected]
Cc: [email protected]; [email protected]
Subject: RE: How to use __MethodParameters in CIM_InstMethodCall

 

Thanks George,

 

The client should use the MethodName parameter to determine the type and
semantics of the returned parameter values  The value of the MethodName
parameter should be a full method path, i.e. <namespace
path>.<className>.<methodName>.

 

What will be the <className> in this case, will it be
"__MethodParameters" or something else? Again, whatever classname I use
it should be compiled in the <namespace path> repository else CIMOM will
throw an exception.

[George] No. the CIM_InstMethodCall indication is in response to the
invocation of a method that would already be defined.  For extrinsics,
the <className> is then the class that defined the method that was
invoked.   I also argue that these indications could be emitted for
intrinsic operations.  In that case, the methodpath is not well defined.
If that is an issue, let me know.

 

 So are you suggesting that I write a __MethodParameters class's mof
file myself and compile it into my working repository??

[George] No.

 

Regards,

Biswapratap,

Wipro Technologies.

From: [email protected] [mailto:[email protected]] 
Sent: Wednesday, May 19, 2010 5:04 PM
To: Biswapratap Chatterjee (WT01 - Semi Conductor and Peripheral IPG);
[email protected]
Cc: Souvik Roy (WT01 - Semi Conductor and Peripheral IPG); Partha Protim
porel (WT01 - Semi Conductor and Peripheral IPG)
Subject: RE: How to use __MethodParameters in CIM_InstMethodCall

 

Instances of __MethodParameters classes are never directly instantiated.
Such instances are only passed as values of the MethodParameters
property of a CIM_InstMethodCall indication.  

 

The encoding of the MethodParameters value allows a client to discover
values for the input or output parameters, as indicated by the value of
the PreCall property.

 

The client should use the MethodName parameter to determine the type and
semantics of the returned parameter values  The value of the MethodName
parameter should be a full method path, i.e. <namespace
path>.<className>.<methodName>.

 

George

 

From: [email protected]
[mailto:[email protected]] 
Sent: Wednesday, May 19, 2010 5:17 AM
To: [email protected]
Cc: [email protected]; [email protected]
Subject: How to use __MethodParameters in CIM_InstMethodCall

 

Hi all,

 

The embedded string object parameter - "MethodParameters" in
CIM_InstMethodCall class is supposed to be used like - 

 

"The parameters of the method, formatted as an EmbeddedObject (with a
predefined class name of "__MethodParameters").

 

Can anybody explain about the actual usage of the predefined class name
- "__MethodParameters"? means should I write a mof having class name as
__MethodParameters containing the union of all the method parameters
that I have used in my implementation or something else. 

 

Thanks in advance.

 

Regards,

Biswapratap,

Wipro Technologies.

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 

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