om: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Robert PorterSent: 28 January 2004
14:41To: [EMAIL PROTECTED]Subject: RE: Periodic COMO
file problem
MFILES is at 52. Don't know if that was the default setting or was
changed by a consultant we work with...
>>> [EMAIL PRO
alf Of Robert PorterSent: 27 January 2004
23:10To: [EMAIL PROTECTED]Subject: Re: Periodic COMO
file problem
It's a Type 1 file. And editing any record even a new one in the file
(really a directory) would result in the problem. I would think, if it was
a bad spot on the disk, predictive sup
PROTECTED] On Behalf Of John
JenkinsSent: 28 January 2004 01:39To: 'U2 Users
Discussion List'Subject: RE: Periodic COMO file
problem
Hmmm
what's your MFILES
?
Regards
JayJay
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf
Hmmm
what's your MFILES
?
Regards
JayJay
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Robert PorterSent: 27 January 2004
23:10To: [EMAIL PROTECTED]Subject: Re: Periodic COMO
file problem
It's a Type 1 file. And editing any record even a new one i
Robert
Other than hardware
related issues (check the disk...) (I see Jerry spotted this one
:-)
The &COMO& file
is really an O/S level directory - when you run ED you are running a BASIC
program which does a READ on a record (file) in the file
(directory).
If the file is massive -
as
It's a Type 1 file. And editing any record even a new one in the file
(really a directory) would result in the problem. I would think, if it was
a bad spot on the disk, predictive support should have shown it by
now. Even if it was bad, everything is mirrored with MirrorDisk/UX, LVM
w/Onlin
I had this happen a couple of times when I worked on an HP
system. Turned out to be a bad spot on the disk drive. Then again how big is the
como file? If the file is large it could take a while to bring it into memory,
if it doesn't get a memory full error first.
- Original Message ---
Here's my "shot in the dark":
I would check the OS tunable dealing with inode and related settings
such as nfile. It's been over a year since I attempted to tune any HPUX
kernels.
Since the &COMO& file is a type 1/19 it's a Unix directory so has
limitations dealing with the native OS.
Now, someo
