Re: STRTCP & STRHOSTSVR

Neil Palmer wrote:
> 
> STRTCP runs STRHOSTSVR since V4R2.
> Recommended way to STRTCP is to add an autostrart job entry to the QSYSWRK
> subsystem, instead of in startup program.
> ADDAJE SBSD(QSYSWRK)   JOB(STRUPTCPIP)   JOBD(QSYS/QTOCSTRTCP)

Thanks, the did the trick!

Any possibility fax support is somehow intertwined?  A long time ago, we
used to have to start and end fax support daily.  Now it, too, starts
automatically.  Right after I removed STRTCP from the startup program
and added the autostart entry, we started getting load form type
messages on the fax writer.  End/start fax support clears it up.  CHGWTR
to say *NOMSG works.  Is it possible that changing when TCP/IP starts
caused this problem?

Here's my theory: immediately after STRTCP in the startup program is the
command that starts all printers (after checking the sysval
QSTRPRTWTR).  I'm thinking that starting TCP/IP took long enough that
fax support initialized before the writers started.  Now, there is no
delay and the AS/400 tries to start the fax writer as a normal writer,
thus causing problems when fax support fully starts.  (I see a message
in the FAXSND01P job that leads me to this conclusion: CPF3310 Writer
FAXSND01P already started.)

I've read on this list that a delay in QSTRUP is no longer needed (that
was related to STRTCP).  That's my answer, though, DLYJOB before
starting printers.  (I'm going to test that tonight anyway, but thought
someone knew a better answer.)  For reference, we are on V4R4.

Thanks for the help!
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---