T.R | Title | User | Personal Name | Date | Lines |
---|
5843.1 | No answer? | TAVIS::ORNA | | Tue Feb 01 1994 06:02 | 4 |
| Is it such a difficult question?
Orna.
|
5843.2 | Not so simple... | TAEC::LAVILLAT | | Tue Feb 01 1994 09:04 | 35 |
| Orna,
I will try to answer your question.
What you describe here is a feature of the Iconic Map PM.
During the creation of the entity, the IM PM will display a form
where you can provide reference attribute 'during' the REGISTER
process.
I say 'during', because in terms of mcc_call, the IM PM will proceed
in 2 steps :
step 1 : mcc_call REGISTER for the entity
step 2 : mcc_call SET references for the entity
So it seems clear that during the REGISTER phase, no reference attribute
is yet defined for the entity.
Your customer has to wait until the whole process is done, and then issue
an mcc_call SHOW reference.
This is not a trivial thing to implement within a AM, since synchronizing
2 mcc_calls is not an easy exercise...
You can try to during the call of the AM REGISTER entry point to create
a background thread that will wait 'for a while' and then perform the
SHOW reference (hoping that it is completed).
Hope this helps.
Regards.
Pierre.
|
5843.3 | Can not operate mcc_call_function | TAVIS::ORNA | | Tue Feb 01 1994 10:33 | 18 |
| Pierre,
Thanks very much for your reply.
We already did this "workaround"; but it did not seem nice.
I had an idea maybe that REGISTER entry point will call an interface
routine which will call 2 procedures:
- first: our original.
- second: will operate the mcc_call SHOW reference.
Is this logically correct?
We tried to operate the 'mcc_call_function' but got an error message,
which says there is no such entry in the FUNCTION dispatch table, which
is correct.....
What you advise?
Orna.
|
5843.4 | map does it all | GOSTE::CALLANDER | | Fri Mar 04 1994 12:16 | 2 |
| As Pierre said, the register doesn't do the show/set at all.
This completely handled by the iconic map.
|
5843.5 | Background process gets stucked. | TAVIS::ORNA | | Thu Apr 21 1994 10:13 | 18 |
| Hello all,
Still the same subject...
As was advised in the previous replies, my customer decided to call to
another process (using "system" system call) which waits for 25
seconds,
then tries to get the information it needs from the MIR in order to
write it to the Sybase DataBase.
This solution seems to be working, BUT.....
From time to time (1 of 7) this background process gets stucked in
different places non-consistently.
We tries to debug it, but could not get any common idea.
Can someone please help?
I can send the code, if nedded.
Thanks in advance,
Orna.
|