Hello all,
Not sure of all the details on this issue. Do we know what was
done or running, system wide, just before this occurred? Upgrade? any back
ground jobs, phantoms or cron?
Another thing that will cause this is an aborted resize. If you
start a resize and abort it, after it has competed the rsz* work file, but
before it has recreated and copied the records back into the original
file, it will leave a 0 byte file. I just tested this and verified it.
cat >/path/to/file or >/path/to/file will do this, but is a
manually performed act and should be easily searched for in existing
scripts, programs, or in users command stacjs in Unidata or in the users
unix shell history.
Thanks.
"Stephen O'Neal" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
10/25/2006 10:00 AM
Please respond to
[email protected]
To
[email protected]
cc
<[EMAIL PROTECTED]>
Subject
RE: [U2] Have you ever seen this?
All,
I think it's pretty cool how many of us came to Tricia's help. We all saw
the predicament she was in.
>From Chuck's response:
When you said "0 bytes", did you really mean zero bytes at the os? Or did
you mean zero records, i.e., an empty data file from the UV perspective?
What was the file's type? ... Static or Dynamic? ...
I spoke with Tricia and she told me static with 0 bytes. It's not a BP
(or program), directory or Dynamic. That's why it's so perplexing.
My vote right now is what Clif, Tim proposed:
cat >/path/to/file
Votes?
Steve
Stephen M. O'Neal
Lab Services Sales for U2
IBM SWG Information Management Lab Services
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
