Re: SQL to replicate iNav's TCP/IP servers

[Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>]

Application Runtime Expert is now included with IBM i.  

Great suggestion since this is what it’s designed for. 


Jim Oberholtzer
Agile Technology Architects

> On Dec 2, 2024, at 4:42 PM, VERNON HAMBERG Owner via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx> wrote:
>
> Hi Dan
>
>
> I suggest looking at Administration Runtime Expert - it's not too costly - check it out at https://www.ibm.com/support/pages/ibm-administration-runtime-expert-i
>
>
> As to pricing, I'm not sure where it sits in the new subscription and no-additional-cost picture.
>
>
> Cheers
> Vern
>
>
> On Mon, 2 Dec, 2024 at 4:23 PM, Dan Bale <dan.bale@xxxxxxxxxxxxxxxxxxxxx> wrote:
>
>
> To: midrange systems technical discussion
>
> Currently, we manually capture various before IPL and after IPL snapshots of active job queues, active subsystems, etc.  I've been tasked with automating this capture so that we can quickly compare the before and after to ensure we're in the same state after IPL as we were before IPL.
>
> iNav's "TCP/IP Servers" does not appear to have any SQL or other programmatical equivalent.  We manually export this to a spreadsheet to capture the Name and Status.
>
> IBM threw out a few suggestions.  The first was to query QUSRSYS.QATOCSTART.  I used:
> select * from QUSRSYS.QATOCSTART
>    where ServerType = 'T'
>    order by ServerType, Server;
>
> While this appears to be close, this query returns one more row than does iNav.  Also, I am unable to match up all the results between the two data sources.  Some are easy, like QATOCSTART's *BOOTP and iNav's BOOTP.  But QATOCSTART will report *HOD (which I presume is Host On Demand) and *NSLD (???), while iNav reports "BootP DHCP Relay Agent" and "RADIUS NAS".
>
> Does anyone have an SQL or other programmatical equivalent to iNav's "TCP/IP Servers"?
>
> - Dan
> *** CONFIDENTIALITY NOTICE: The information contained in this communication may be confidential, and is intended only for the use of the recipients named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please return it to the sender immediately and delete the original message and any copy of it from your computer system. If you have any questions concerning this message, please contact the sender. ***
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx>
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx>
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription related questions.
>
> .
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.