| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1102.1 | record length | DGOSW0::GUESDON | | Thu Jun 06 1991 11:49 | 1 |
| I've forgotten in .0 to say that our record is 527 bytes long...
|
| 1102.2 | | VERNA::V_GILBERT | | Thu Jun 06 1991 13:15 | 7 |
| Can you be more specific about what you are trying to do in the
Iconic Map:
Are you doing a show of a partition or a show current value of
a particular attribute or what?
Verna
|
| 1102.3 | | DGOSW0::GUESDON | | Thu Jun 06 1991 16:09 | 2 |
| We're doing a "SHOW <my specific entity> ALL <partition>" ... by clicking the
appropiate menu of DECwindows.
|
| 1102.4 | | VERNA::V_GILBERT | | Thu Jun 06 1991 16:57 | 8 |
| Do you mean that you are setting Operation Mode to listbox and then selecting
from the operation list box the operation show and then each of the partitions
for this entity, thus bringing up several management windows.
If so, try doing each show operation separately to see which is giving you
the problem.
Verna
|
| 1102.5 | ilv buffer not large enough | TOOK::HAO | | Fri Jun 07 1991 11:56 | 12 |
| I can't tell whether the ILVTOOBIG message is coming from the PM
itself, or whether it's being returned by your module. In general,
I believe the message means that the ILV buffer is not large enough
to contain the values that you are trying to encode. Since this is
a SHOW command, my guess would be that your module tried to encode
values into out_p, and ran out of space. This status is returned
from one of the mcc_ilv_put routines. Is your module catching this
status and making sure to return MCC_S_INSUF_BUF to the PM and
specifying the out_p size that you need?
Christine
|
| 1102.6 | the status is normal | DGOSW0::GUESDON | | Wed Jun 12 1991 06:30 | 7 |
| 1. I'm not using the list box in this precise problem, so the SHOW
command is trying to access only one partition.
2. We have no error message from the ILV routines that we are using in
our module (anyway we have put the apropriate tests in it). So we
suppose that the problem doesn't come from our AM...
|
| 1102.7 | a couple of testing suggestions | TOOK::KOHLS | Ruth Kohls | Wed Jun 12 1991 20:12 | 19 |
|
> 2. We have no error message from the ILV routines that we are using in
> our module (anyway we have put the apropriate tests in it). So we
> suppose that the problem doesn't come from our AM...
>
The error MCC_S_ILVTOOBIG only comes from ILV or ASN routines.
I really think it is most likely coming from the AM in this case -- that is a
large record. I would suggest that after the mcc_ilv_put_param_end call
succeeds, you dump the encoded buffer with mcc_ilv_dump. That will show that
the AM is indeed correct and what the encoding looks like.
You might also try testing with FCL and turning on the log bit that will dump
the ilv encoding --please check this! but I think its MCC_FCL_LOG set to 8.
that will allow you to see whether the record is coming back through the call
interface correctly.
Ruth
|
| 1102.8 | one more thing... | TOOK::KOHLS | Ruth Kohls | Thu Jun 13 1991 12:17 | 9 |
| Christine,
> This status is returned
> from one of the mcc_ilv_put routines.
The ILVTOOBIG status can also be returned by mcc_ilv_get.
Ruth
|
| 1102.9 | define mcc_fcl_pm_log 8 | TOOK::CALLANDER | Jill Callander DTN 226-5316 | Fri Jun 14 1991 13:46 | 0 |
| 1102.10 | Problem with desframe routine ? | DGOSW0::GUESDON | | Mon Jun 17 1991 13:10 | 9 |
| We had already seen the output ILV by defining mcc_fcl_pm_log to 8, and
the ILV coding seemed to be correct...
But since my preceeding note, we noticed that the problem comes from
the mcc_desframe_set_cvr_and_reply: if we build by ourselves the outp
parameter (i.e. we don't use the design framework routine), this problem
disappears.
But now we have got the problem described in note 1103 ...
|
| 1102.11 | which part of 1103? | TOOK::CALLANDER | Jill Callander DTN 226-5316 | Mon Jun 17 1991 19:40 | 0 |
| 1102.12 | Note 1103.0 (unexpected info message) | DGOSW0::GUESDON | | Tue Jun 18 1991 03:51 | 1 |
|
|
| 1102.13 | | TOOK::CALLANDER | Jill Callander DTN 226-5316 | Mon Jul 08 1991 13:16 | 4 |
| sorry for the delay in responding, I have been out.
Just curious, did you resolve the unexcepected info problem?
|