================================================================================ Note 3.13 Run-Time problems 13 of 19 VXCERN::TIMBL "Tim Berners-Lee CERN/DD" 18 lines 13-JUN-1988 12:02 -< "No I/O channels available" with Ethernet and BI >- -------------------------------------------------------------------------------- When using raw ethernet communications under VMS on a BI machine using a DEBNT interface, OPAL have noticed problems when using many protocol types on the same machine. It seems that whether they are used by RPC or other applications, after 6 or so, the error "No I/O channels available" is given. This error message normally refers to VMS I/O channels, for which there is a process quota, but in this case it must be refering to something else. 1. It is dependent on the number of processes using raw ethernet in the SYSTEM. 2. The error is returned not by $ASSIGN, but by the QIO which does IO$_SETMODE call to configure the channel. It is at this point that the buffers are requested and the protocol type specified. My wild guess based on these facts is that there is some limit on the ability of the DEBNT interface to multiplex different protocol types, but it could be a modifiable system parameter. No cure found yet. ================================================================================ Note 3.14 Run-Time problems 14 of 19 VXCERN::TIMBL "Tim Berners-Lee CERN/DD" 6 lines 25-JUN-1988 13:42 -< re 3.13 >- -------------------------------------------------------------------------------- Normal Gee noticed that if you raise the some of the memory parameters (non-paged dynaic memory) and one of the cluster parameters, you can raise the limit on protocol types. See also a problem described in note FNAL::SYSTEMS 79.0 which seems to be different but similar.