bad file number error

[Walter Vaughan]

Cesar Baquerizo wrote:

> Thanks for the reply;  the error message I get is cryptic.  It does 
> not give me a reference that I can make out.  It looks exactly as 
> written below.
> I've done some searches and found reference to this error and write 
> statements (which this table does have).  Could that be a problem?  It 
> is a very straightforward statement???

Okay, the write / close sequence is the problem. The write tries to 
globally push all the data it can from all open files. In your case now, 
something is not ready to be written. Remove the write. By definition 
the "close fmctrl" will write the data and close it., so the write is 
not needed.

>
> *** A System Error Has Occurred ***
> : Bad file number
>
> The statement is:
>
> gettsno■ 
> If:                                                                   ■
>       Then: 
> rn(2,.0)="1"                                                      ■
> 45  -------   -   -   -   -   -   -   -   -   -   -   -   -   -   -   
> -   -
>       ■ 
> If:                                                                   ■
>       Then: lookup fmctrl  r=rn   
> -ep                                         ■
> 46  -------   -   -   -   -   -   -   -   -   -   -   -   -   -   -   
> -   -
>       ■ If: aa eq 
> ""                                                          ■
>       Then: aa=fmctrl(2) ; fmctrl(2)=fmctrl(2) + "1" 
> ;write                   ■
> 47  -------   -   -   -   -   -   -   -   -   -   -   -   -   -   -   
> -   -
>       ■ 
> If:                                                                   ■
>       Then: close 
> fmctrl                                                      ■
> 48  -------   -   -   -   -   -   -   -   -   -   -   -   -   -   -   
> -   -
>       ■ 
> If:                                                                   ■
>       Then: return         
> ---------------------
>
> Cesar Baquerizo
>
> ces at cescom.com
> Off. - (718) 343-0829
> Fax. - (718) 343-3111
> Cell - (917) 685-8447
>
> http://www.linkedin.com/in/cbaquerizo
>
>
> ********************************************************************
>
> This message and any attachments are solely for the intended 
> recipient. If you are not the intended recipient, disclosure, copying, 
> use or distribution of the information included in this message is 
> prohibited.
>
> If you received this message in error, please notify the sender and 
> permanently delete.
>
>
>
>
> Walter Vaughan wrote:
>
>> Cesar Baquerizo wrote:
>>
>>  
>>
>>> I have a problem with an openserver 6 system running filepro v4.5
>>>
>>> *** A System Error Has Occurred ***
>>> : Bad file number
>>>
>>> This error came up on a process that was working fine for years on 
>>> sco openserver 5.  In fact the migration to OS 6 was done on Monday, 
>>> and the error just came up today for the first time.  This process 
>>> is done several times a day, so it is not the first time this 
>>> process is run.  This one is critical, so any help appreciated.  Any 
>>> clues as to what causes this?
>>>  
>>>
>>>     
>>
>> In our case, it was poorly written code that got fleshed out in our 
>> move from SCO OSR5 with filePro 4.05.09 to FreeBSD with filepro 5.0.13.
>>
>> And poorly written isn't the correct term. filePro on SCO just seemed 
>> to be more forgiving with how/when/where you close or write I/O type 
>> files. However, we were doing the "wrong thing". That combination  
>> (SCO & fp) would do the right thing anyway or not complain at all.
>>
>> What filePro verb is causing the Bad file number error?
>>
>> -- 
>> Walter
>>
>> _______________________________________________
>> Filepro-list mailing list
>> Filepro-list at lists.celestial.com
>> http://mailman.celestial.com/mailman/listinfo/filepro-list
>>   
>
>
>