| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
Hello,
These two questions are from a customer who is in the process of wrting
an AM to manage some specific terminal servers, they are running into
some difficulties with ILV encoding.
1) They would like to know how to calculate the size of an ILV buffer?
i.e. what is the overhead per construction etc...
2) When called by the Control_Fm on a show directive, the out-P buffer
is 1024 bytes long. Their out-P construction is over 4000 bytes long.
As the out-p is static, they cannot deallocate it to return a longer
buffer. What is the workaround for this problem ?
Thanks for your help,
Philippe.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1066.1 | TOOK::SWIST | Jim Swist LKG2-2/T2 DTN 226-7102 | Wed May 29 1991 12:56 | 13 | |
1) Have the AM put the size it really needs in mcc_w_curlen in the
out_p descriptor.
2) Set the handle to MORE (presumably you would save a pointer to
what you were doing when you ran out of space in the handle context).
3) return MCC_S_INSUF_BUF (CVR, not an exception).
4) You will get called back with a buffer of the size you need.
The above is doc'd in the SRM.
| |||||
| 1066.2 | We had read the SRM... | DGOSW0::GUESDON | Thu May 30 1991 14:05 | 5 | |
The point 2 concerning the Handle is apparently not specified in the
SRM...
Thank you for your help.
| |||||
| 1066.3 | page 324 in SRM | TOOK::CALLANDER | Jill Callander DTN 226-5316 | Thu May 30 1991 15:46 | 7 |
chapter 10 on the call interface describes in detail the interworkings of all the call fields. The section on "mcc_call Interface Condition Values Returned", 10.5.11, describes the insuf_buf error and the need to set the handle to more. It's there but you really need to know your SRM to find it. Chapter 10 can be real helpful in understnding things. | |||||
| 1066.5 | estimating ILV encoding size | TOOK::KOHLS | Ruth Kohls | Wed Jun 05 1991 14:14 | 16 |
1) They would like to know how to calculate the size of an ILV buffer?
i.e. what is the overhead per construction etc...
The overhead is approximately 4 bytes per put_param_begin/end and
put_cons_begin/end. For an attribute in an attrib_list, you have 24 bytes per
attribute in addition to the value. That figure includes the reasoncode and
datatype encodings. A real datum (double, or 8 bytes) is encoded in
10 bytes, most of the other primitive datatypes take about as many bytes
in ILV as they do out of it, rounded up.
Currently, there is a hard limit of 32500 Bytes per complete ILV encoding,
and ILV will not accept a buffer of less than 10 bytes.
Ruth
| |||||