Note that option 4 on that screen isn't necessarily ending the job and
instead is issuing the ENDTCPCNN command. This doesn't guarantee the job
will end and instead only that the TCP connection is ended. This has
different consequences depending on the language you are using and can
sometimes put the corresponding job into a race condition. Better to end
the job instead of the TCP connection.

I learned the hard way on this one awhile back :-)

Aaron Bartell
litmis.com - Open Source and IBM i. No Limits.


On Thu, Aug 20, 2015 at 3:35 PM, Kelly Cookson <KCookson@xxxxxxxxxxxx>
wrote:

Never mind. I figured out that I could use NETSTAT, option 3 and look for
my port number. Then take option 4 to end the job. That seems to have
worked.

Thanks,

Kelly Cookson
IT Project Leader
Dot Foods, Inc.
1.217.773.4486 ext. 12676
kcookson@xxxxxxxxxxxx



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.