Larry Simonsen wrote:

> daily our backup procedure stops the jnetd job and does a netcontrol stop
> before the backup and then netcontrol start;net==lan1 and net=loop and
> stream jinetd.every day between 7-8 am (about 4-5 hours after jinetd starts)
> the job starts into a condition that it consumes all CPU. doing a showq the
> job is always in the list and the ftp server does not respond.  aborting the
> job and restreaming the ftp service is alive for the rest of the day.  what
> could possibly be wrong?

Larry, I was just reviewing patch digests this morning and remembered
seeing something like what you've described. In the description for
patch NSTFD10A (General Fixes for NS TRANSPORT on MPE/iX 5.5 (C0)
Patch), the following is included:

>   SR: 1653-224386
> FROM: NSTEDV3
> Fix for JINETD "hangs" in the process of establishing new connection.
> If the connection is CLOSED because of some error then return proper
> error in the procedure tcp_set_ptid so that the telnet code PTID_INIT
> need not loop for re-trying.

Maybe someone is trying to connect as soon as JINETD is started, perhaps
even before it's finished starting, and causing it to hang. You might
call HPRC and find out if you need NSTFD10A (if you don't already have
it).

HTH,
Patrick
--
Patrick Santucci
Technical Services Analyst
KVI, a division of Seabury & Smith, Inc.
Visit our site! http://www.kvi-ins.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Alcohol and calculus don't mix. Never drink and derive.
               ~ Anonymous (but sounds like Wirt Atmar)