Re: STRTCP & STRHOSTSVR

Well, you could add an autostart job entry for Fax.  If it's still in the 
startup program the situation you mention is possible I suppose.
TCP will start when the first subsystem is started (QSPL - which will 
cause QSYSWRK to start).  However, the startup program will not wait while 
TCP/IP starts, so yes I guess you could try a DLYJOB before the start 
print writers in the startup program.
If the STRFAXSPT has been moved to an autostart job, maybe you might want 
to put it back in the startup program, to ensure it's run before the print 
writers are started.  Or change the 'writers to autostart' for the fax 
output queues to zero.

I'm on V4R5 and don't notice any attempt to start a writer for the fax 
output queues when the startup program is run.
Are you using the default fax output queue names (QFQ.......) ?

Neil Palmer      DPS Data Processing Services Canada Ltd.
50 Acadia Avenue, Ste.102                   AS/400~~~~~
Markham, Ontario, Canada.   ____________          ___  ~ 
Phone:(905) 474-4890 x303   |OOOOOOOOOO| ________  o|__||= 
Cell.:(416) 565-1682 x303   |__________|_|______|_|______) 
Fax:  (905) 474-4898         oo      oo   oo  oo   OOOo=o\ 
mailto:NeilP@DPSlink.com  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
http://www.DPSlink.com     iSeries 400  The Ultimate Business Server
 




Sean Porterfield <sporter@bestdist.com>
Sent by: owner-midrange-l@midrange.com
2001/01/29 13:10
Please respond to MIDRANGE-L

 
        To:     MIDRANGE-L@midrange.com
        cc: 
        Subject:        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
+---