T.R | Title | User | Personal Name | Date | Lines |
---|
281.1 | I may have seen it... | TUNER::COPPERSMITH | SYSTEM-W-RELFLT, reality fault | Tue Nov 07 1989 12:33 | 7 |
| FOCUS loves to confuse alphanumeric with numeric. In general,
delimiting a numeric string with alpha characters (say, subroutine
parameters...) will force focus to alpha interpretations, but this
does you no good. I'm also curious as to whether you are near the
maximum number of characters for the expanded file path.
CJC
|
281.2 | | CURRNT::OTTEN | Inscrutibles Unscrewed.. Free | Fri Nov 10 1989 10:46 | 8 |
| Focus under MRE uses numeric subdirectories.. ie [user.a1.nnn]..
with no problem..
Hope this helps...
David
|
281.3 | /subdir bug ? | AYOV18::MCONNELLY | | Fri Oct 19 1990 04:58 | 58 |
|
I have discovered a problem with FOCUS/SUBDIR which is causing major
problems for me.
When I invoke FOCUS without the subdir qualifer everything works fine.
However, if I invoke FOCUS with the /SUBDIR qualifer it loses my
data file logicals as used in the filedef. It somehow manages to
translate the logical and obtain the file name (without the directory
name) but then prefixs the filename by FOC$TMP: This happens only
when the first reference to the file is made (eg table file)
eg. logical CDC$$F_ST_PRODT_REF is set prior to invoking FOCUS.
assign $4$DUA22:[CDC010.DAT]CDC_D030_010.IDX CDC$$F_ST_PRODT_REF
$FOCUS/SUBDIR
>>? FILEDEF
SYSIN TERMINAL
SYSPRINT TERMINAL
OFFLINE PRINTER
FOCSTACK DISK_USER04:[CONNELLYM.20C076D9]FOCSTACK.FTM
CDCDS001 LOGICAL (CDC$$F_ST_PRODT_REF:)
** files filedef correctly
>>TABLE FILE CDCDS001 PRINT ST_PRD_CD
>END
** when access master it can't find
** the file.
FOCSAM CALLED TO READ DATA
%RMS-E-FNF, file not found
(FOC1049) ERROR IN READING NEXT RECORD :
** do a filedef and suddenly file
** is in FOC$TMP !
>>? FILEDEF
SYSIN TERMINAL
SYSPRINT TERMINAL
OFFLINE PRINTER
FOCSTACK DISK_USER04:[CONNELLYM.20C076D9]FOCSTACK.FTM
CDCDS001 FOC$TMP:CDC_D030_010.IDX
My application will have multiple users, and I am trying to use a
standard development environment, therefore utilising the /SUBDIR=delete
functionality prevents the need to set up different permanent
subdirectories for each user.
I have also tried this with the file specification of 30 characters
but still had the same problem.
Does anyone know a way around this problem. ?
Is it possible to assign FOCSTACK & FOCSORT to different file
for each user ?
Any help will be appreciated.
Martin.
|
281.4 | | MILPND::MADDEN | | Tue Oct 23 1990 16:38 | 2 |
| Did you try setting foc$dir1 to the location where the master
description is??
|
281.5 | i've already tried foc$dir1 | AYOV27::MCONNELLY | | Wed Oct 24 1990 08:53 | 3 |
| I tried setting foc$dir1,foc$dir2 to master area it didn't make
any difference. It actually finds the master, its the data file
logical which is affected.
|
281.6 | | MILPND::MADDEN | | Fri Oct 26 1990 10:17 | 2 |
| When you set the filedef, is there a colon after the logical?
like this FILEDEF FILE1 DISK LOGICAL:
|
281.7 | using colon after logical name | AYOV27::MCONNELLY | | Mon Oct 29 1990 08:27 | 2 |
|
Yes, there is a colon after the logical name.
|
281.8 | Why Won't it Run ??? ....
| PAKORA::SACAMPBELL | If at first you don't succeed, cheat!! | Mon Jun 10 1991 08:22 | 21 |
| There hasn't been a subdir problem for a while so I thought I'd post one.
I've been trying to get some Focus routines running using Focus/Subdir to solve
a problem we are experiencing at the moment with two Focus routines trying to
write to the same FOCSORT.FTM file at the same time.
I got one of the production Focexec in my own are and tested it out and lo and
behold no problem. I thought no change would be needed to the focexec to make
it run, just invoke focus with FOCUS/SUBDIR=DELETE.
I tried this on our production account and the job would not run.
There was nothing called to read data. No lines held. Just a couple of
chevrons.
The Focus procedure has not been changed at all. It will run on one account and
not the other.
Can anybody help.
Stuart.
|