Re: Verify network connection from i

If you've got PASE and yum installed, both Python and Perl have socket
libraries.

On Tue, Aug 21, 2018 at 11:04 AM, David Gibbs <david@xxxxxxxxxxxx> wrote:

On 8/21/2018 11:53 AM, Rob Berendt wrote:

I think we're looking for a batch method of testing communications.
Kind of like the right options on PING will allow you to use a
MONMSG. Are there options on TELNET to say not to use TN5250? Are
there options on TELNET to allow a batch mode and use MONMSG like
PING does?

No, I'm fine with interactive ... this isn't for programmatic testing.
I'm looking for a good way to diagnose a problem.

david


--
David Gibbs
midrange.com

IBM i on Power Systems: For when you can't afford to be out of business!

I'm riding 615 miles (Yes, you read that right) in the American Diabetes
Association's Tour de Cure to raise money for diabetes research, education,
advocacy, and awareness. You can make a tax deductible donation to my ride
by visiting https://lsteml.diabetessucks.net.

See where I get my donations from ... visit
https://lsteml.diabetessucks.net/map for an interactive map (it's a
geeky thing).


I may have diabetes, but diabetes doesn't have me!
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

--
Absolute Performance, Inc.
12303 Airport Way, Suite 100
Broomfield, CO 80021

NON-DISCLOSURE NOTICE: This communication including any and all
attachments is for the intended recipient(s) only and may contain
confidential and privileged information. If you are not the intended
recipient of this communication, any disclosure, copying further
distribution or use of this communication is prohibited. If you received
this communication in error, please contact the sender and delete/destroy
all copies of this communication immediately.