Re: Netserver startup -- MIDRANGE-L

Subject: Re: Netserver startup
From: Patrik Schindler <poc@xxxxxxxxxx>
Date: Wed, 6 Dec 2023 10:45:28 +0100
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

Hello Mark,

Am 05.12.2023 um 23:47 schrieb Mark Waterbury <mark.s.waterbury@xxxxxxxxxxxxx>:

Without those newer APIs on V4R5, perhaps you could just issue:
VFYTCPCNN RMTSYS('127.0.0.1')
or PING RMTSYS('127.0.0.1')

and then check the diagnostic and completion messages that are returned by this command, to determine if TCP/IP is actrive?

Thanks! That's the direction I probably need to go.

:wq! PoC

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Netserver startup , 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.