|
Hello William,
I'm afraid your solution doesn't suit me.
What I need in fact is something like that :
. routine mcc_mir_get_instance()
input parameter : an identifier of the entity instance
I'm looking for
output parameter : the entity instance
(a kind of mechanism of backtranslation).
Thank's for help,
regards,
sylviane.
|
| Typically when people talk about entities in the MCC sense they talk
about Class / Instance pairs. If you have a global entity, it has a
unique class. You know your own class, you do not need a routine call
to get it. Also if you have a fullname identifier, it is also unique.
However, the source code may not know it's value at any given time.
The instance is made up of one or more identifiers, the primary
identifier must always be available, and possibly one or alternate
identifiers. The term "instance" is more general than identifier, and
implies that the value is of one identifier datatype and you don't care
which one. (The point is: IF YOU HAVE AN IDENTIFIER, THEN YOU HAVE AN
INSTANCE.) Sorry, if I'm not explaining this well.
In your case, the instance is one of two possible identifiers. A
fullname identifier, and a "concatenated" identifier. If you want to
go from "concatenated" (i.e., alternate) identifier to primary
identifier, you call translate_ident. If you want to know what all the
identifiers are, you call get_identifiers. If you already have an
identifier (and hence an instance), then just call mcc_aes_create.
Pass in your unique class code and the instance(/identifier) that you
have, and you have an entity spec. My understanding of the
backtranslation tree is allow translation of a non-fullname identifier
to a fullname identifier (and possibly vise-versa) through the use
of dns softlinks. The MIR routines do not use the DNS backtranslation
trees. They translate from one identifier to another by matching up
UIDs.
There should be nothing missing. The MIR routines are just primitive
routines. But, there may be something in the toolkit which does more
for you.
-Matt.
|