[prev in list] [next in list] [prev in thread] [next in thread] 

List:       caldera-netware
Subject:    Re: Netware semaphores ?
From:       "Vladimir V. Kolpakov" <w () lv ! net>
Date:       1999-01-29 0:41:54
[Download RAW message or body]

    How to do selection: how many function from list below
_not_ supported by Netware for Linux ?


    Have anybody a bit knowledge about location NCP function list
on the Net, or its strongly proprietary?


On Wed, Jan 27, 1999 at 11:30:24PM +0200, Vladimir V. Kolpakov wrote:
> On Tue, Jan 26, 1999 at 05:34:07PM -0700, Chris Clark wrote:
> > NCP [Function 34/Subfunction 0] is "TTSIsAvailable", which checks to see
> > if the server supports Transaction Tracking.
> > 
> > The documented completion codes for NCP 34/0 are:
> > 0	Transaction Tracking Unavailable
> > 253	Transaction Tracking Disabled
> > 255	Transaction Tracking Available
> > 
> > Since NWL does NOT support Transaction tracking, NWL should should return
> > Completion Code 0, which means "TTS Unavailable".
> > 
> > All other TTS NCP functions (i.e. NCP function 34, subfunction!=0) will
> > return ccode 251, which is UNSUPPORTED_REQUEST.
> > 
> > In any case, NWL does not provide TTS services.  If your application
> > requires TTS, NWL won't work for you.
> 
>     There is full (I hope:) list of NCPs,
> used by the nasty application:
> 
> -------------------------------------
> [...]
> .....                                    fn: 104
> NCP request: conn: 5, seq: 152, task: 2, fn: 104, subfn: 1  , NDS call
> NCP request: conn: 5, seq: 160, task: 2, fn: 104, subfn: 2  , NDS call
> NCP request: conn: 5, seq: 156, task: 2, fn: 20
> NCP request: conn: 5, seq: 168, task: 2, fn: 22 , subfn: 1
> NCP request: conn: 5, seq: 155, task: 2, fn: 23 , subfn: 17
> NCP request: conn: 5, seq: 153, task: 2, fn: 23 , subfn: 28
> NCP request: conn: 5, seq: 159, task: 2, fn: 23 , subfn: 29
> NCP request: conn: 5, seq: 154, task: 2, fn: 23 , subfn: 55
> NCP request: conn: 5, seq: 117, task: 1, fn: 24
> NCP request: conn: 5, seq: 158, task: 2, fn: 25
> NCP request: conn: 5, seq: 0  , task: 4, fn: 26
> NCP request: conn: 5, seq: 3  , task: 4, fn: 30
> NCP request: conn: 5, seq: 254, task: 4, fn: 32
> NCP request: conn: 5, seq: 209, task: 4, fn: 34 , subfn: 0
> NCP request: conn: 5, seq: 118, task: 1, fn: 62
> NCP request: conn: 5, seq: 119, task: 1, fn: 63
> NCP request: conn: 5, seq: 123, task: 1, fn: 66
> NCP request: conn: 5, seq: 245, task: 4, fn: 68
> NCP request: conn: 5, seq: 219, task: 4, fn: 71
> NCP request: conn: 5, seq: 121, task: 1, fn: 72
> NCP request: conn: 5, seq: 2  , task: 4, fn: 73
> NCP request: conn: 5, seq: 120, task: 1, fn: 76
> [...]
> -------------------------------------
> 
>     I wonder if there exists detailed list of NCPs anywhere.
> Seems like "34, subfn: 0" is not doing anything useful,
> since "TTSIsAvailable" request doesn't do much.
> 
> 
> 
> -- 
> --w
> 

-- 
--w

[prev in list] [next in list] [prev in thread] [next in thread]