The behavior of ping according to TCP/IP status might differ depending on the version. You can easily test it when running a restricted state for your save 21, as TCP/IP is (normally) ended.When the gateway becomes reachable, remaining of 999 packets will be sent quickly, and the ping command will end. You can, immediately after, start QSPL subsystem and start the writers with QSYS/QWCSWTRS program and start your applications.I'd have expected ping to exit with an error immediately if TCP/IP isn't started. So this is a very interesting approach!! Need to tinker around with that idea! Thanks a lot for that!
There are API to help (for instance Retrieve TCP status), but a lot of them were introduced with V5R1.Probably need to have a look. To not hard code any values, it would be nice to obtain the default gateway address but that's for sure contained in a PF. 😄
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.