>>> ----------
From: David_Kellerman at nls.com[SMTP:David_Kellerman at nls.com]
> Sent: Friday, March 21, 1997 2:10 PM
> To: bpenteco at boi.hp.com> Cc: pmp at pwg.org> Subject: RE: PMP> chNetwarePServer channel type problem?
>> Bob Pentecost <bpenteco at boi.hp.com> wrote (edited):
>> > I'm sending this to the general PWG PMP list to make everyone aware of this
> > problem and it's going to Bob Setterbo and Scott Isaacson to get some
> > Novell help to answer the questions (I don't remember which of you was
> > involved when this was added to the Printer MIB).
> >
> > From the 3-14-97 version of the Printer MIB I find:
> >
> > PrtChannelTypeTC ::= TEXTUAL-CONVENTION
> > STATUS current
> > DESCRIPTION
> > "This enumeration indicates the type of channel that is
> > receiving jobs.
> >
> > This is a type 2 enum."
> > SYNTAX INTEGER {
> > <bunch of values deleted>
> > chNetwarePServer(10), -- Novell, Inc.
> > -- prtChannelInformation keywords:
> > -- Server Name
> > -- Keyword: "Server"
> > -- Syntax: Name
> > -- Status: Mandatory
> > -- Multiplicity Single
> > -- Description: The name of the server on which
> > -- the queue resides.
> > --
> > -- Queue
> > --
> > -- Name: "Queue"
> > -- Syntax: Name
> > -- Status: Mandatory
> > -- Multiplicity Single
> > -- Description: The name of the queue on the
> > -- server
> > --
> > -- NDS Tree
> > --
> > -- Keyword: "NDSTree"
> > -- Syntax: Name
> > -- Status: Mandatory
> > -- Multiplicity Multiple
> > -- Description: The NDS Tree SAP name
> > --
> > -- NDS Queue
> > --
> > -- Keyword: "NDSQueue"
> > -- Syntax: Name
> > -- Status: Mandatory
> > -- Multiplicity Single
> > -- Description: The name of the queue object in
> > -- the associated NDS Tree
> > -- There must be exactly one Server and one Queue
> > -- entry or exactly one NDSTree and one NDSQueue
> > -- Entry.
> > <bunch of values deleted>
> >
> > The description says "There must be exactly one Server and one Queue entry
> > or exactly one NDSTree and one NDSQueue Entry." However, the HP JetDirect
> > card for our printers can serve up to 16 server/queue pairs over one
> > channel, so we need to allow multiple entries. Also, we can support NDS and
> > the other type in various combinations.
> >
> > The questions are:
> >
> > 1) Why is there a limit of one or the other? I think multiple and mixed
> > Server/Queue and NDSTree/NDSQueue pairings should be allowed.
> >
> > 2) Why does NDSTree specify "Multiplicity Multiple" but the rest of the
> > keywords are "Multiplicity Single"?
> >
> > Unless I'm missing something, I suggest the last sentence for
> > chNetwarePServer(10) be changed to: "Keyword entries must be paired (Server
> > followed by Queue or NDSTree followed by NDSQueue) and may be repeated."
>> If I understand the situation correctly (I'm no NDS expert, so bear
> with me, but I was in the middle of defining the prtChannelInformation
> entry), 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.
>> :: David Kellerman Northlake Software 503-228-3383
> :: david_kellerman at nls.com Portland, Oregon fax 503-228-5662
>>
What is multiplicity for if I can't specify multiple queues being serviced? We have a single Novell channel that services multiple queues.
Bob Pentecost
HP