Pegasus Telecon Minutes

7 Feb 2002: 12:00 est approx 1 hr

FileName: Document3

Author: K. Schopmeyer

Modification Date: 2/7/2002 11:04 AM

# 1 Logistics

# 2 Agenda

Discuss the current major technical problems and either define solutions or actions to arrive at solutions.

# 3 Attendees

Barbara P, HP

Tony, Compaq

Rudy, Compaq

Roger, HP

Mike B

Mike D

KS

# 4 Notes

## 4.1 CIM Control Services Functions

Discussion of the CIM Control services functions – Mike working on defintion. We want to make it as simple as possible. Question: Can we start with the old provider manager for provider 2,

Mike believes he will have a definition complete in a couple of days and will distribute the defintion.

Question from Roger, Tracking requests sent to providers – Their goal is knowing about outstanding transactions when preparing to shut down the provider and the CIMOM.

Want to be able to know if a provider has outstanding operations? It is in the provider manager. Need to find out if there is a way to get access to number of outstanding operations.

ACTION: Include this function. Needed by HP. Mike Day believes Chip already knows about this and will review the code to determine if it is in the code now

Question from Roger - Invoke Method operation . Only return today is the return value. Note that the Invoke method also has output parameters whch we are apparently not considering. We must provide for returning these return parameters also

ACTION: Review this and add the capability to return output parameters from invoke method. The API has cim value in the response handler and no way to return the output parameters.

ACTION: Put this on the project plan. Develop a new response handler for this function.

NOTE: Nobody specifically assigned to this task as of today

Roger – Work out how the indication consumer manager works. This is the function that manages consumers and gives indications to people that want them. This thing will work off of registrations for URLs so that indications can be sent to the correct consumer. The question is combining the functions of provider manager and consumer-provider manager. Should indication consumers be treated off of the provider manager or should there be a separate consumer manager.

There are two steps here, loading and instantiating. We can either add the indication consumer interface to the provider manager or create a new consumer manager.

PROPOSAL: use the provider manager. It is probably easier to add to the provider manager than create a new manager.

ACTION: Be sure this on the work list. Review with Chip. Make this part of the functions to discuss with Chip. This is an estectic issue, pollution of the provider interfaces, etc. Note that the priority of this is below that of the dispatcher.

Roger asked the question “If a provider is loaded by two different managers you will have problems with the shutdown process, etc?” Mike Day’s answer is that The actual DLL should be protected by the OS from unloads before all users of the dll by usage counts.

Roger noted that the Consumer indication interface has been submitted and is in the consumer directory as the indication consumer. This is the interface that they want the consumer provider to use to receive indications.