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



Guys:

I have created a DASD daily usage utility using DSPOBJD, CLP,QRY and embeded
SQL.  This utility works fine for information display, reporting and for all
object types analysis.

These are my observations:
1.    Empty libraries are not returned by DSPOBJD (see detail command
below), not a big deal.
2.    Using WRKSYSSTS, my DASD size is 41.94Gig, %used is 92.3845, my
utility
        reports about 76% used (30.89Gig), this is a big deal.
3.    What happened to 16% of DASD, where in the system can I find this used
storage or
        is there a good explanation for the hidden space.

This command was ran once for control data and could be run again to change
control data
=============================================================
DSPOBJD OBJ(*ALL/*ALL) OBJTYPE(*ALL) +
    DETAIL(*BASIC) OUTPUT(*OUTFILE) +
        OUTFILE(PULSEOBJS)

This command is run every night to compare with control data and to show
usage
======================================================
DSPOBJD OBJ(*ALL/*ALL) OBJTYPE(*ALL) +
    DETAIL(*BASIC) OUTPUT(*OUTFILE) +
        OUTFILE(PULSEOBJSZ)

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.