T.R | Title | User | Personal Name | Date | Lines |
---|
2811.1 | more around this issue | OASS::VALDEZ_C | A smile is the same in any language | Tue Jun 08 1993 17:41 | 22 |
| Hi,
I spoke to another person at the same customer site concerning this issue.
I asked her to supply me with the output from the GOLD/W after calling the
entry form and getting the error. The output was:
OA-E-DB NOFILE FORM QK-DSAB DOES NOT CONTAIN A VALID .FILE SPECIFICATION
OA-E-DD_MIS_ACT_QUAL, NO /ACTION QUALIFIER FOUND IN THE CURRENT .FILE
DIRECTIVE
OA-E-EIF ERROR OCCURRED WHILE FORM ENTGETKEY WAS CURRENT
My guess is that now that there is a /ACTION qualifier, the code is being more
specific in its check of the entry form directives. V2.4 had no such
qualifier and therefore specific checks were not as necessary. Could this be
the case? The customer is very anxious for an aswer or any suggestions. If
they have to write their own action routines they are willing to try, but they
want to know if there is any other "easy" way to regain the same functionality
that they had in V2.4.
Thanks a lot for any help.
Cindy Valdez
|
2811.2 | | IOSG::MAURICE | Night rolls in, my dark companion | Tue Jun 08 1993 17:56 | 13 |
| Hi,
Yes you're right - it was the new /ACTION qualifier that is the
difference. A couple of thoughts:
a) Can your customer change to use a different special character than
"/"?
b) If using logicals try a logical name that contains a ".", e.g. "a.b"
Cheers
Stuart
|
2811.3 | problem with "." in logical name | OASS::VALDEZ_C | A smile is the same in any language | Tue Jun 08 1993 21:34 | 37 |
| Hi Stuart,
Thanks so much for your reply.
> a) Can your customer change to use a different special character than
> "/"?
The customer says that the "/" is required.
> b) If using logicals try a logical name that contains a ".", e.g. "a.b"
I had the customer try this (using the LOGICAL function) and she didn't get an
error about the slash; she got a "file not found". I then tried to do this at
DCL.
$ DEFINE/SYS/EXEC MY.FILE SYS$LOGIN:LOGIN.COM
If I do
$ DIR MY.FILE
it looks for a file with that name. If I do
$ DIR 'F$TRNLNM("MY.FILE")'
that works and finds LOGIN.COM.
So, I think this might work, but I don't know the way to define a logical with
a period so that DCL will honor it or to tell the .FILE directive to do
something analagous to F$TRNLNM on that logical. What am I doing wrong?
Thanks again!
Cindy
|
2811.4 | Try 2 levels of logical name | IOSG::CHINNICK | gone walkabout | Wed Jun 09 1993 13:17 | 20 |
| Hi Cindy...
I've had a quick look at this problem and it seems that the code tries
to translate the .FILE entry as a logical unless it has a filespec
character like ":", "[", "<" or ".".
The problem is that it checks for a "/" first and expects to find
/ACTION if a slash is present.
You should be able to get around this as Stuart has suggested using a
logical with a "." in it OR by having a 2 level translation:
$ DEFINE X Y
$ DEFINE Y ".../..."
then .FILE X wont see the "/"
Now, I can't say that I've tested this, but I think it'll do the trick.
Paul.
|
2811.5 | thanks - waiting for results from customer | OASS::VALDEZ_C | A smile is the same in any language | Thu Jun 10 1993 15:52 | 12 |
| Hi Paul,
Thanks a lot for looking at the code and for your suggestions. I've tried the
double level logical here and it doesn't complain about the slash, just about
file syntax (which makes sense because I don't have that DTF type of file
here). I'm trying to get in touch with the customer to have her test. I'll
post results.
Thanks again!
Cindy
|
2811.6 | did .4 work? | IOSG::VOWLES | Raphael VOWLES DTN 830 6910 REO2 G/M2 | Tue Jul 20 1993 16:49 | 5 |
| I have the same problem here.
Cindy - did .4 work out?
Please post results. tta rv Tuesday 20-JUL-1993 15:49
|