× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi Robert,

Cant you use three part naming to link to the remote lpar's?

This link should help, the example is very useful:-

https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/ddp/rbal1intro.htm

Thanks,
Karl.

              

-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Robert Wenzel
Sent: Monday, November 2, 2020 8:35 AM
To: rpg400-l@xxxxxxxxxxxxxxxxxx
Subject: Gathering Object Statistics Across LPARs

We have four LPARs. One contains our source repository and test databases/schemas. The other LPARs contains databases and program objects deployed from the source LPAR.
I am writing an SQLRPGLE program to create an Obsolete Objects table for review and potential retirement from our source repository.
I need to be able to gather the object statistics (more specifically the Last Used Date of objects) from the other three LPARs while residing on the source repository LPAR.
Anyone know how I can get Object Statistics from another LPAR while resident on another LPAR?
I can run this SQL statement on the local LPAR but cannot figure out how to get this data from LPAR2, LPAR3 and LPAR4 while I am on LPAR1.
Any suggestions other than populating an output file on each LPAR separately and then combining later?

select objname, date(Last_used_timestamp) as LastUsedDate, objtext from table (QSYS2.OBJECT_STATISTICS('LIBRARY','*PGM') ) AS X order by objname ;;


As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.