Thanks for the variable hint. Yes it was an application that produced the
error. The application uses a system variable that stangely was not set on
rebooting the system.
-----Original Message-----
From: Dr. Thomas.Blinn_at_Compaq.com [mailto:tpb_at_doctor.zk3.dec.com]
Sent: Wednesday, May 30, 2001 11:09 AM
To: Andre Thompson
Subject: Re: Error - Bad file unit number
> Hi Managers
> Does anyone know what a "bad file unit number" error message
> is and how can I solve it?
>
> Best Regards
> Andre Thompson
Doh.. Any more context than that? When are you seeing this message?
Is it coming out of some user application? Sounds to like the kind
of thing you might get out of a mis-behaving Fortran program, since
Fortran uses file unit numbers and they can be in variables and the
variables can get trashed by program logic errors (bugs). Other than
that, doesn't look real familiar..
Oh, yeah, is this happening on a Tru64 UNIX system? Version number?
And so on..
Tom
Dr. Thomas P. Blinn + UNIX Software Group + Compaq Computer Corporation
110 Spit Brook Road, MS ZKO3-2/W17 Nashua, New Hampshire 03062-2698
Technology Partnership Engineering Phone: (603) 884-0646
Internet: tpb_at_zk3.dec.com - or - thomas.blinn_at_compaq.com
ACM Member: tpblinn_at_acm.org PC_at_Home: tom_at_felines.mv.net
Worry kills more people than work because more people worry than work.
Keep your stick on the ice. -- Steve Smith ("Red Green")
My favorite palindrome is: Satan, oscillate my metallic sonatas.
-- Phil Agre, pagre_at_alpha.oac.ucla.edu
Yesterday it worked / Today it is not working / UNIX is like that
-- apologies to Margaret Segall
Opinions expressed herein are my own, and do not necessarily represent
those of my employer or anyone else, living or dead, real or imagined.
Received on Wed May 30 2001 - 15:21:44 NZST