|
STRDSKRGZ will not do what you want. What it does is essentially "defrags" your disks. Sounds worthless to me, as I have heard that it apparently did to IBM, but customers kept asking for it, so IBM provided it. "Always keep the customer satisfied." You need RGZPFM, assuming that you have deleted records to reorganize out. This will tie up the physical file, and all related LF's for the use of the command. Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com "Kincer, Alan" <akincer@xxxxxxxx m> To Sent by: "'midrange-l@xxxxxxxxxxxx'" midrange-l-bounce <midrange-l@xxxxxxxxxxxx> s@xxxxxxxxxxxx cc Subject 05/16/2003 11:30 <Start Disk Reorganization> AM questions Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxx nge.com> 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 ======================================================================= This e-mail, including any attachments, contains information from KI (USA) Corporation which may be confidential or privileged. These contents are intended only for the individual(s) to whom it is addressed. If you are not the intended recipient do not copy, distribute, or take any action in reliance on it. If you have received this e-mail in error notify the sender immediately via message reply then delete or destroy all electronic and hard copies of the communication, including attachments. KI (USA) Corporation's anti-virus system checks for known viruses. Accordingly you are advised to run your own virus check before opening any attachments received. KI (USA) Corporation will not accept any liability once an e-mail and/or any attachment is received. Views expressed in the e-mail are those of the author and not necessarily those of KI (USA) Corporation. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx 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 mailing list archive is Copyright 1997-2025 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.
midrange.com
