×
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, probably. I'm not a big fan of CPF0000. I'd prefer knowing WHY it
failed. For example, let's say your program was recompiled and someone
forgot to adopt authority or some such animal. And the reason it dies is
because it cannot run ENDTCP. Should this just be ignored and go on?
However if it dies because TCP/IP is already dead, then that would be an
acceptable message to ignore.
You want to know the really funny thing? Read the help on ENDTCP. Not
one of the messages you can monitor for begin with CPF. So your MONMSG
CPF0000 does nothing (unless you do not have authority to the command or
some such thing). Please just put the message id's from the help
associated with:
- &1 not active.
- TCP/IP already ending with *CNTRLD option.
But, other than that, your program should work. Hopefully the STRSBS
(&QCTLSBSD) starts your TCP/IP back up.
Rob Berendt
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.
midrange.com
