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



Alan

STRDSKRGZ is the defragment command for the 400. A Knowledge Base article has more to say. <http://www-1.ibm.com/support/docview.wss?uid=nas1e6f5ea2c8c14d1508625670600726566&rs=110>. It's not for the files. It should be run when you get CPI0997 - Nearly all available machine addresses used. Reason 1 in QSYSOPR

I advise first checking how much space is lost to deleted records. Run

DSPFD *ALLUSR/*ALL TYPE(*MBRLIST) FILEATR(*PF) OUTPUT(*OUTFILE) OUTFILE(SOMELIB/FDMBRLIST)

and

DSPFD *ALLUSR/*ALL TYPE(*ATR) FILEATR(*PF) OUTPUT(*OUTFILE) OUTFILE(SOMELIB/FDATRPF).

SELECT sum(PHMXRL * (MLNRCD + MLNDTR)) totsize, sum(PHMXRL * MLNDTR) dltsize
FROM vern/fdatrpf, vern/fdmbrlist
WHERE PHFILE = MLFILE and PHLIB = MLLIB

will give you an idea of any problem. It'll also tell you about how much of total disk is in use by the physical files.

SELECT MLLIB, MLFILE, MLNAME, PHMXRL * (MLNRCD + MLNDTR) totsize, PHMXRL * MLNDTR dltsize, mlndtr / (mlnrcd + mlndtr) pctdlt
FROM vern/fdatrpf, vern/fdmbrlist
WHERE PHFILE = MLFILE and PHLIB = MLLIB and mlndtr <> 0
ORDER BY pctdlt desc


Check with your vendors, to see if they depend on RRN order for anything. If not, consider changing the physical files to REUSEDLT(*YES). Candidates are files that have ADD/UPD/DLT activity - you can see this with DSPFD TYPE(*MBR) - look for those with high percent deletes over writes.

HTH

Vern

At 11:30 AM 5/16/2003 -0400, you wrote:
Arrgh! I am at 85% storage space on my 9406-170 and according to PM400
reports am in the "critical" zone. Performance has gotten pretty sluggish
during the day but I do not know if this is directly tied in to this.

Anyway, I am familiar with reorganizing files...pretty much database file
compaction to weed out holes left from deleted records and reindexing I
suppose. I also know that it is difficult sometimes to get this to work on
the files that need it most since the program has to have exclusive access
to the object (usually a high-volume production table).

But in trying to reclaim disk space over the entire 400 I ran across command
STRDSKRGZ. This looks like a good command for the job but I had a couple of
questions:

It seems to be an "open ended" command that requires I set a time limit or
nomax. Obviously I would like it to do the complete disk system. Does it
stop when the entire disk is reorganized or does it just keep going?

If I run it for a set length of time what are the implications behind that?

Does it have the same "file lock" limitations as RGZPFM? If so I would have
to have everyone off the system apparently.

Any advice is appreciated.

Alan



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.