× 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.



I live and die by the RTVDSKINF and the PRTDSKINF *SYS combo.
However, I've had serious issues on RTVDIRINF and PRTDIRINF. On one
machine, that is top of the line and normally is begging for some work to
keep it busy because it is so undertaxed I have seen RTVDIRINF and
PRTDIRINF run for days. Other machines, and lpars, no problem. They are
a prime example of how not to do SQL. (Run them in debug.) Since then,
I've not messed with their files that much.

And you're right, those field names would not bode well for native i/o in
RPG. That's not used to stuff like GRAPHIC and DBCLOB. But the reason
for those is that directory names can be thousands of characters long, and
full of DBCS.

You're going to have to do your analysis in SQL.

Try this (changing QAEZD0007 to what pertains in your situation)
SELECT SUBSTR(char(QEZOBJNAM),1,30) AS ObjectName,
SUBSTR(char(QEZDIRNAM1),1,60) as DirName,
QEZOBJTYPE, QEZALCSIZE, QEZDTASIZE,
QEZACCTIM, QEZCHGTIMA, QEZCHGTIMD
FROM QUSRSYS/qaezd0007o O
JOIN QUSRSYS/QAEZD0007D D
ON O.qEZDIRIDX = D.qEZDIRIDX
order by qezalcsize desc

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.