| 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 |
I have a question related to the error message returned when partial
wildcarding is not supported.
The SRM (V1.0 p 67) mentions :
"An error return will result from the inappriopriate use of partial
wildcarding that is distinct from the one that indicates wildcarding
not supported."
The only common exception that I have found is :
MCC$_K_UNSUPP_ENT_WILDCARD : Unsupported wildcard in entity
specification.
The sample AM also returns this common exception on partial wildcarding.
Is there a common exception defined for partial wildcarding or is it an
SRM error ?
Regards,
Marc.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 30.1 | INFO - invalid entity identifier versus no wild | GOSTE::CALLANDER | Fri Dec 08 1989 17:39 | 22 | |
I think what the SRM is getting at is that inappropriate wildcarding
can usually be caught by the the parser when attempting to interpret
an entity instance. This will result an error being generated by
the TRM. Once an entity has been encoded then it is up to the FM
or AM to determine if they support wildcarding. If they do not
then the user will get the unsupported message.
At this point the sample am does not support partial wildcarding
that is why the error. If you try something like partial wildcarding
of an entity with a data type that is not defined as supporting
partial wildcarding, you should see the parser error.
An example is to do a station command which takes an ethernet address.
These address do not support partial wildcarding as part of the
data type definition; so the command returns an invalid entity instance
error.
MCC> sho station 00-88-*
%MCC-E-INVALIDIDENT, Invalid entity identifier
MCC>
| |||||