× 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 ran into the same issue trying to use the query the tool mentions.

I changed the query to substring the DIRNAME field, now it  looks like:

SELECT
        COUNT(*) AS "Number of Objects",
        SUM(CAST(st_size AS DEC(31))) AS "File Size",
        SUM(CAST(st_allocsz AS DEC(31))) AS "Allocated Size",
        SUBSTR(dirname,1,200) AS "Directory"
FROM
        qryifslib
GROUP BY
        SUBSTR(dirname,1,200)


-------------------------
 Bryan Dietz
3X Corporation
614-410-9205







"Urbanek, Marty" <Marty_Urbanek@stercomm.com>
Sent by: midrange-l-admin@midrange.com
07/29/2002 08:01 AM
Please respond to midrange-l


        To:     "'midrange-l@midrange.com'" <midrange-l@midrange.com>
        cc:
        Subject:        IFS space usage, QRYIFSLIB


Update: I cut the DIRNAME field back to 1500 and recompiled the program
and
that eliminated the SQL error.

However, I still have my same basic problem of not being able account for
all the space occupied by "user directories."

Thanks,
-Marty
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.






As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.