I'm not familiar with the Pick(r) DUMP command, but you can peer into a
group with fileview...
Simple syntax:
$UDTBIN/fileview -g1 VOC
You can dump blocks using the -b option (useful for overflow blocks -
chasing the links).
Different arguments for part files in dynamic files, etc.
Also - Colin typoed with the 6.0 option for 'zapping' a group. fileview
-gn -zv FILENAME (group n, 'z'ap, 'v'erify (eg prompt 'are you
sure'))
No fileview is not documented. Designed as an engineering tool. Originally
designed to GENERATE file corruption to test 'guide'. So - be careful. If
you just type the command with no arguments, it spits out 2 pages of syntax
- you can see the 'randomly generate' options... skip 'em.
There are a number of examples of using this utility on slides in the
presentations I've made at conferences over the past few years and are on
the infamous 'survival kit cd'.
Wally Terhune
Manager - U2 Advanced Technical Services
IBM Information Management Solutions
Tel: 303.294.4866 Fax: 303.294.4832
[EMAIL PROTECTED]
www.ibm.com/software/data/u2/support - Open, Query, Update, Search -
Online!
"Alfke, Colin"
<[EMAIL PROTECTED]
> To
Sent by: <[email protected]>
[EMAIL PROTECTED] cc
stserver.u2ug.org
Subject
RE: [U2] broken dynamic file on UDT
03/08/2005 06:57
AM
Please respond to
u2-users
Chuck, I feel your pain. I've spent the good part of the last two weekends
fixing a similar problem. I'm not sure how big *very* large is in your
world is, in mine it was about 3GB.
Guide didn't find an error in the file but it would coredump when certain
items were "fi"led. Programs trying to write the file received similar
errors.
I managed to copy out the records in the "bad" group (RECORD HISTFILE
'35676354'). Strangely enough they copied out OK. I deleted the indices. I
then used fileview with the -nv option to wipe the group. Then memresized
the file (with memory 512000 - it's much faster), with the same paramters.
Checked the group and ran guide. Re-ran memresize with a completely
different modulo and block size. I made sure the items I copied out didn't
exist and copied them back in. Lastly, the invoices were rebuilt. The file
appears to be OK now. This was all done while all other users were off of
the system.
It's times like this that I miss the Pick DUMP command. It lets you see
exactly what is in the group so you know what it was unable to pull out.
All of this was interspersed with efforts of dumpgroup, fixgroup, a routine
(clean.group) from IBM that programatically ran the fileview commands to
clear the group, adding space to the filesystem (reboot to make sure the
dynamic file can see the new space). At one point sms -F to see the space
on the system was just going wacky.
It was on UniData 6.0.8 on Aix 5.1.
Colin Alfke
Calgary, AB
[demime 1.01d removed an attachment of type image/gif which had a name of
graycol.gif]
[demime 1.01d removed an attachment of type image/gif which had a name of
pic16748.gif]
[demime 1.01d removed an attachment of type image/gif which had a name of
ecblank.gif]
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
