| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 4482.1 | | VERNA::V_GILBERT | | Tue Feb 02 1993 15:17 | 3 |
| Was the parent of the child partially registered?
Verna
|
| 4482.2 | No. | TAVIS::ORNA | | Wed Feb 03 1993 09:06 | 3 |
| No, it was fully registered.
|
| 4482.3 | | VERNA::V_GILBERT | | Wed Feb 03 1993 10:58 | 7 |
| Was it perhaps registered before you upgraded to a T1.3.x version. Several
algorithms have changed as well as some management specifications have changedl
To tell if this is the case, deregister the entity in question, then re-register
it and see if the problem still exists or has gone away.
Verna
|
| 4482.4 | It's V1.2. REGISTER may help? | TAVIS::ORNA | | Thu Feb 04 1993 04:27 | 6 |
| We are using V1.2. We have not upgrades it ti T1.3.
Is we add the REGISTER directive to the child entity, would it
solve the problem, maybe?
Orna.
|
| 4482.5 | global v.s. child view | POLE::LEMMON | | Thu Feb 04 1993 11:37 | 21 |
| When you say "map", do you mean a global view (e.g, when
you open a domain) or do you mean a child view (e.g.,
when you double-click into an entity)?
If you add a child to a global view, the Iconic Map
issues a CREATE and REGISTER directive (providing they
exist). The display information (e.g, x,y coordinates)
are stored in the map file upon saving it. If you do not save
the map before you either exit or open a new domain, the child
will not be displayed the global view the next time the
domain is open.
The child view does not have a map associated with it.
The iconic map, when you navigate into the entity,
issues either the SHOW or DIRECTORY directive to retrieve
the entities children. The SHOW is used if the entity class
has DYNAMIC = TRUE. DIRECTORY is used if DYNAMIC = FALSE.
SHOW goes to the agent for the info while DIRECTORY goes
to the Registration database.
/Jim
|
| 4482.6 | More detailed description | TAVIS::ORNA | | Mon Feb 08 1993 02:39 | 22 |
| OK, I'll try to be more precise and describe what my problem is.
We have CREATED a child entity nad saw it on our map.
We poped-up ti its father (global entity) and double click on
its father again. At that time we were not able to see the child
entity we already had created.
Since double clicking on a global entity activates the command
SHOW <ge-name> <ge-instance> <che-name> * ALL IDENTIFIERS,
we tried to activate this command in the FCL. Using the debugger
we could not even stop in the show routine, it crashes with the
message: MCC-MMABORT: target management module thread has aborted.
The commnad SHOW <ge-name> <ge-instance> <che-name> * ALL STATUS
operates OK. The routine for 'show identifiers' is exactly the
same as for 'show status' but differs in the data returns.
In order to try to understand why we are not able to stop in
the 'show identifiers' routine, we change the entry in the
dispatch table so the 'SHOW ...... <ch-name> * ALL STATUS' command
will call the 'show identifiers' routine, and indeed we were able
to get to the 'show identifiers' routine, .....
So, can you please help me to see what the problem is?
Orna.
|
| 4482.7 | dispatch table might be out of date | GOSTE::CALLANDER | | Wed Feb 10 1993 09:58 | 15 |
| you haven't by chance been playing any games with your class codes?
It is possible that your dispatch table is confused. You might want
to try to reenroll your module, or completely delete the dispatch
table and enroll everything again. Also you can check this
from the test bed.
manage/tool/test (ultrix mcc_tbd)
deposit verb 2
deposit attribute 1
dump/access
The above will dump all show identifier commands that are currently
loaded in the dispatch table.
|