Many of the problems related to JINETD.NET.SYS are associated with the fact
that the job stream as delivered is designed to run in the job default
queue of DS.

The job should be modified so that it executes in the CS queue.

To do this, edit JINETD.NET.SYS to add ";PRI=CS" to both the job statement
and the run statement. (Actually one or the other should suffice but both
makes one feel more assured).

Additionally, you must ensure that jobs can indeed execute in the CS queue.

You can assure that by including JOBPRI 0,DS or JOBPRI CS,DS in your
SYSSTART.PUB.SYS file after first executing one of the commands from the
console prior to aborting, then re-streaming the modified JINETD.NET.SYS.

I cannot guarantee you this will solve all of your JINETD problems - but
from my experience, it has helped on many occasions - and it won't hurt.

Incidentally, I wish JINETD would be enhanced to date/time stamp the
connection messages appearing in $STDLIST. It would be so easy to do, and
so useful.



At 08:12 AM 11/13/99 +0100, Ogunsanya A.T. wrote:
>Good People,
>
>Top of this beautiful day to you.
>
>I need any assistance or suggestions anybody might just have on a
>little problem I have been facing on our HP3000.
>
>For quite sometime now, the job INETD.NET.SYS has been reporting some
>messages on the console :
>COULD NOT GET SOCKET RECORD POINTER FOR TELNET DEVICE
>
>Whenever this message starts appearing on the console, the System
>refuses new Telnet connections but the running sessions will still
>continue to run.
>Before, the message goes on for like 10 minutes and it stops and
>everything comes back to normal. This happens like 3 times in month
>before but now, it happens maybe once in a week and lasts longer than 10
>minutes.
>We have had situations that the INETD job reports this for over 30
>minutes and it takes actual rebooting of the machine to get it back to
>normal.
>
>Yesterday morning, we got the same message on the console and it went on
>for like 40 minutes before we had to take down the System and bring it
>back up. Everything went back to normal after rebooting but sometimes in
>the afternoon, the message started appearing again but went off by
>itself after 5 minutes.
>
>We were running MPE 5.5 Release 4 but we recently applied PowerPatch 7.
>
>I will like to have suggestions or comments or any experience whatsoever
>and advice on how this problem can be solved once and for all.
>
>Thank you for your time and hoping to hear from you all !
>
>I am,
>Akinyemi
>
>
---------------------------------------------------------------------------
Gilles Schipper
GSA Inc.
HP3000 & HP9000 System Administration Specialists
300 John Street, Box 87651   Thornhill, ON Canada L3T 7R4
Voice: 905.889.3000     Fax: 905.889.3001
Internet:  [log in to unmask]
---------------------------------------------------------------------------