[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | FOCUS, from INFORMATION BUILDERS |
|
Moderator: | ZAYIUS::BROUILLETTE |
|
Created: | Thu Feb 19 1987 |
Last Modified: | Mon May 05 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 615 |
Total number of notes: | 1779 |
176.0. "PROBLEM MY FEXs ARE DEAD FOC302" by BPOV04::CHEUNG () Mon Jan 30 1989 12:18
I had this big problem. Experts, please help me to solve it:
I wrote a small reporting routine call 936PR.fex.
This fex program worked fine until I include it in a
command file and submit the command file in batch.
When I came back the next day, I found out that the
program boomed. Error message is FOC302, error writing
to the Temporary file.
Ever since then, I could not run the any .fex files from
my account. It booms at the first focus instructions,
giving the same message (FOC 302). I copy the same .fex file
to my friend's account and it works.
I checked the memory and there is enough. I would like to
know 1) why did it boom? 2) Can I submit .fex as a batch
and 3) what should I do now? Thank you
I call IBI_FOCUS hotline but they are of little help.
Jeffrey
DTN- 296-3680
T.R | Title | User | Personal Name | Date | Lines |
---|
176.1 | Too many sessions? | MEMV01::COPPERSMITH | SYSTEM-W-RELFLT, reality fault | Mon Jan 30 1989 16:37 | 10 |
| This sort of thing often happens when you are trying to run an
interactive and a batch session against the same focstack or focsort
files. You must establish separate working directories for each
simultaneous focus session in your account. Try:
delete/log [...]*.ftm;* from your root directory and then try to
run a .fex again. Then include code in your batch procedure
establishing a separate working directory.
Curtis Coppersmith
|