>>> <David_Kellerman@nls.com> 03/21/97 02:10pm >>>
> the way the prtChannelTable is organized, your example would
> break out into multiple prtChannelEntry objects. Each of these would
> have its own prtChannelInformation value, and they might potentially
> differ in other prtChannelEntry fields.
Dave K states it exactly as I remember it. There was much discussion
about this: how to encode multiple pairs? The solution was multiple
entries in the table. If this is broken, I am sure other types will have to
As for Bob's question:
> 2) Why does NDSTree specify "Multiplicity Multiple" but the rest of the
> keywords are "Multiplicity Single"?
As I go back and re-read this, it looks like it must have been a
cut and paste error. Probably should be single. I still have to think
about it some more to remove some of the cobwebs.