| 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 |
With the T1.1.0 kit, an mcc_ilv_put of a DT_SUBRANGE value results in %MCC-F-ILVNOTIMPLYET, ILV hasn't implemented this ASN.1 type yet A release note or a code change is called for, as appropriate.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 547.1 | use the basetype | TOOK::HAO | Thu Dec 13 1990 12:14 | 10 | |
Richard,
When ilv encoding a Subrange datatype, use the base type in the
mcc_l_dt field instead of MCC_K_DT_SUBRANGE. For example, if in
your MSL, you have: TYPE myint = 1 Integer8 [5..10], then use
MCC_K_DT_INTEGER8. This is how the PMs are supporting Subrange
datatype.
Christine
| |||||
| 547.2 | Is this the right strategy? | COOKIE::KITTELL | Richard - Architected Info Mgmt | Thu Dec 13 1990 13:30 | 7 |
Thanks Christine. So the strategy is that the DT is still sub-range in the dictionary, and the PMs will do range valdidation on input, but we move the values through ILV as the base-type? | |||||
| 547.3 | yup... | TOOK::HAO | Fri Dec 14 1990 12:42 | 4 | |
You got it!
Christine
| |||||