| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 297.1 | define as an enumeration | TOOK::HAO | | Fri Aug 31 1990 15:13 | 10 |
| To use the Entity Existence argument, you have to define the
datatype in your own MSL as an enumeration, exactly as specified in
the Datatypes chapter of the SRM. You then encode it as an
enumeration.
I believe the SRM will be made clearer in a future release with regards
to this and other similar datatypes.
Christine
|
| 297.2 | My own MSL for a common exception ?? | TENERE::DUNON | Paul Dunon - Telecom Engineering - VBO | Mon Sep 03 1990 09:49 | 20 |
| RE .1
How can I define this datatype in my own MSL, and then use it as the
datatype of the ARG_ENT_EXIST argument of the MCC_K_OP_ILLEGAL common
exception ??
Here is an example of what I'm trying to do:
mcc_cvr = sample_am_put_exception (
MCC_K_OP_ILLEGAL,
&MCC_K_ARG_ENT_EXIST,
&0, /* Entity exists */
MCC_K_DT_ENTITYEXISTENCE,
MCC_S_COMMON_EXCEPTION,
context->mcc_reply);
What's wrong with that ?
-- Paul
|
| 297.3 | still have to encode as enum | TOOK::HAO | | Tue Sep 04 1990 09:15 | 34 |
| Sorry, I thought you tried to use this datatype for your own
specialized exception, in which case, you would have to define it in
your own MSL.
However, even for a common exception, you still have to encode it as an
enumeration as defined in Chapter 9. Simply specifying
MCC_K_DT_ENTITYEXISTENCE will not work. Use MCC_K_DT_ENUMERATION
in the datatype field, and the value is one of the following (defined
in the COMMON section of the dictionary):
DAP> show defin constructor_data_type
Definition Name = CONSTRUCTOR_DATA_TYPE
Type = T Length = 115 Count = 1 Defined = TRUE Class = S
Usage = ILV
(
1 = (
0 = %X 456E7469747920457869737473 -- "Entity Exists"
1 = %X 456E74697479204578697374656E63652043616E
6E6F742042652044657465726D696E6564 -- "Entity Existence
Cannot Be Determined"
2 = %X 456E7469747920496E61636365737369626C65 --
"Entity Inaccessible"
3 = %X 456E7469747920556E6B6E6F776E -- "Entity
Unknown"
4 = %X 456E74697479204E6F6E4578697374656E74 -- "Entity
NonExistent"
) )
Christine
|
| 297.4 | Thanks | TENERE::DUNON | Paul Dunon - Telecom Engineering - VBO | Wed Sep 05 1990 05:38 | 7 |
|
Thanks Christine, it works as you said.
But I don't understand when and how we could use the
MCC_K_DT_ENTITYEXISTENCE data type ?
-- Paul
|
| 297.5 | not really datatypes | TOOK::HAO | | Thu Sep 06 1990 10:06 | 11 |
| The datatypes that are defined enumerations in Chapter 9 are not
considered to be "real" datatypes (i.e. entity existence, persistence).
They are to be treated as normal enumerations. I don't believe that
there are any plans to treat them specially in MCC.
The SRM will be updated in a future release regarding these kinds of
datatypes.
Hope this helps,
Christine
|
| 297.6 | enumerations defined in the datatypes chapter | TOOK::KOHLS | Ruth Kohls | Tue Sep 11 1990 13:46 | 27 |
|
The following "datatypes" are used in exceptions and are
actually enumerations, not datatypes:
MCC_K_DT_PERSISTENCE
MCC_K_DT_QUALIFIERTYPE
MCC_K_DT_ENTITYEXISTENCE
Look in Ch 15 of the SRM for how they are expected to be used.
For the Kernel AM, I use the MCC_K_ARG_<pick one>
in the mcc_l_id field of a descriptor, and MCC_K_DT_ENUMERATION, as
Christine said, in the mcc_l_dt field.
The enumeration "attrib op reason code" is what is supposed to be
used in all those "ReasonCode" arguments for List Mode ILV
encoding of attributes.
None of these four should be defined in mcc_interface_def, but
since they are, we will have to phase them out.
They are in, and belong in, the mcc_common_definitions.ms (and .h, etc)
|