This may or may not help. I have seen this type of error at our site. But
most sites may not be setup like we are.

We have a separate file system setup for our _PH_, _HOLD_ and SAVEDLISTS.
The theory being that if we have a runaway report or some other event fills
up this file system, we won't corrupt our Unidata files.

The setup of an account in this structure requires us to  remove the _HOLD_,
SAVEDLISTS and _HOLD_ after running newaccount. The VOC pointers are set to
point to the separate file system for these files. And everything works fine
while you are within Unidata in a normal terminal session.

The place where we encounter errors is if we forget to symbolically link
these files at a UNIX level. So from UNIX, we need to be able to 'cd' to
_HOLD_, SAVEDLISTS and _PH_ if everything is setup right. Once this step is
done, our problems disappear.

Just thought I would throw this out in case your account setup is some what
non standard. - Rod

-----Original Message-----
From: Dan Eichholz [mailto:[EMAIL PROTECTED]
Sent: Monday, July 12, 2004 4:10 PM
To: [EMAIL PROTECTED]
Subject: RE: [U2] capturing problem


I can't help solve your problem, but I get a very similar error on Unidata
5.2 and 6.0 on solaris 8. Maybe some additional observations will help
someone out there figure out both problems if they are indeed the same.

For us, the error occurs during a sequence of unidata calls from the command
line (cron) and phantom is not involved. Our cron script runs about 30
unidata calls sequentially on a variety of accounts. Usually they last for
less than a second. This whole sequence repeats every 10 minutes. We get 0
to 3 of these per day with no consistent time or correlation to server load.

It is highly unlikely that our problem is permissions (for us) as there is
only 1 user id that initiates calls to unidata on the production accounts.

Unix command:
  echo "$*" | udt | tail +8 | /usr/xpg4/bin/grep -vx ":"
Ouput:
  cat: cannot open _PH_/webster40980_14962

We were unable to get answers from IBM since we couldn't reliably reproduce
it.
If you find out what it is, I'd certainly appreciate it if you could pass
the info on.

Dan Eichholz
(Internet Production, Inc.)

> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of John Reid
> Sent: Friday, July 09, 2004 3:54 PM
> To: [EMAIL PROTECTED]
> Subject: [U2] capturing problem
>
>
> We've been getting this error in u2 - 10.08 with PICK.FORMAT for quite a
> while. It happens only on a few applications and very frequently for those
> applications.
>
> The error message is:
> Unable to create capture file. The error code number is 020291.
> It runs as a
> phantom, and so is only spotted if someone looks at the &PH& files or the
> errlog. I believe that we have support calls in on the matter,
> but I havent
> heard any resolution.
-------
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/

Reply via email to