× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Well, at V5 you don't have STRTCP in your startup program because it's 
controlled by the parameter in CHGIPLA - and the AutoStart attribute set 
for the SMTP server will control that (a "shortcut" to setting TCP server 
autostart parameters - UPDDTA QATOCSTART - keep the *YES/*NO in caps).

MSF is usually started by an autostart job entry in the QSYSWRK subsystem:
                        Display Autostart Job Entries 
 
Subsystem description:   QSYSWRK        Status:   ACTIVE
 
Job            Job Description     Library 
QZMFECOX         QZMFEJBD          QSYS 

...Neil




"Condon, Mike" <M1C@xxxxxxxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
2004/10/24 16:16



To
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
cc

Subject
SMTP/MSF in Qstrup






What is the recommended method to get SMTP mail relay/MSF started in
Qstrupgm? There is strtcp strsvr(*yes) strifc(*yes) in the cl, but from 
what
I'm experiencing it does not insure that smtp/msf are functional. 

Should I: 
- After STRTCP STRSVR(*YES) STRIFC(*YES), add STRTCPSVR SERVER(*ALL) 
- Just add STRMSF after STRTCP?

If I do either, do I need to somehow handle or issue a delay before 
starting
the commands to insure that STRTCP has progressed far enough or finished 
to
make sure MSF or other servers will indeed start properly?
--





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.