| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1126.1 | any errors during PTB? | TOOK::HAO | | Wed Jun 12 1991 10:04 | 11 |
| I know you've mentioned that you rebuilt the parse tables, but I just
wanted to double-check that you rebuilt them after installing the
Translan AM.
It sounds as if the parser is not recognizing the Translan commands,
since you can't access them from FCL and you can't register it from
the Iconic Map (Iconic Map uses the parser when adding entities to the
map).
Christine
|
| 1126.2 | Make sure that your latest parse tables are in MCC_SYSTEM:MCC_PTB_PARSER.BPT | MCDOUG::MCPHERSON | i'm only 5 foot one... | Wed Jun 12 1991 11:16 | 4 |
| And check for previous versions of MCC_PTB_PARSER.BPT lying about in
likely areas (e.g. SYS$SPECIFIC:[MCC], etc).
/doug
|
| 1126.3 | No special error on PTB | GOYA::MERINO | Angel Garc�a Merino - ACT ENS Spain | Wed Jun 12 1991 13:16 | 25 |
| The only message I got building the parse table was:
...
Processing entity 17 3
Processing entity 17 3 2
Processing entity 17 3 25
Processing entity 17 3 26
Processing entity 17 4
Processing entity 17 5
Processing entity 17 6
Processing entity 17 6 8
Processing entity 17 6 9
Processing entity 17 27
Processing entity 17 27 18
Processing entity 17 27 19
%MCCPTB-I-NOENTRY, No dictionary entries found.
No attributes defined for entity class.
Processing entity 17 27 19 21
Processing entity 17 27 20
Processing entity 17 27 22
Processing entity 17 27 23
Processing entity 17 27 24
...
Of course this rebuild was done after Translan AM software installation.
Thanks,
Angel.
|
| 1126.4 | Problem solved! | GOYA::MERINO | Angel Garc�a Merino - ACT ENS Spain | Wed Jun 12 1991 13:38 | 5 |
| Problem solved after moving the MCC_PTB_PARSER.BPT file from MCC_COMMON to
MCC_SPECIFIC.
Thanks all,
Angel.
|
| 1126.5 | I love it when I'm right! ;^) | MCDOUG::MCPHERSON | i'm only 5 foot one... | Wed Jun 12 1991 14:27 | 4 |
| I only had to do that to myself about 5 or 6 times before I started just
changing my default directory to MCC_SYSTEM before doing any PTB stuff...
/doug
|
| 1126.6 | where should the parse table live? | PARZVL::KENNEDY | This ain't no party | Mon Jun 17 1991 17:54 | 12 |
| >Problem solved after moving the MCC_PTB_PARSER.BPT file from MCC_COMMON to
>MCC_SPECIFIC.
Is this the _right_ fix? I've just noticed that I've got
MCC_PTB_PARSER.BPT in both MCC_SPECIFIC and MCC_COMMON. Seems to me that
this should live in MCC_COMMON. Could this be (or have been) a problem with
installation of DECmcc or one of the extra kits?
Shouldn't we really move the current version into MCC_COMMON and get rid of
any versions in MCC_SPECIFIC?
_Mek
|
| 1126.7 | mcc_system is used | TOOK::CALLANDER | Jill Callander DTN 226-5316 | Wed Jun 19 1991 13:06 | 7 |
| we use the mcc_system logical to find the parse tables. If you had to move
a copy of it from common to specific, that means you already had one in
specific.
Note mcc_systme is a search list, specific to common.
jill
|
| 1126.8 | | COL01::WELZEL | Uwe Welzel, Nac, Cologne | Fri Jun 28 1991 16:19 | 16 |
|
-< what about VAXcluster >-
>we use the mcc_system logical to find the parse tables. If you had to move
>a copy of it from common to specific, that means you already had one in
>specific.
>Note mcc_systme is a search list, specific to common.
you're right Jill, but what happens if you work in a VAXcluster enviroment
with different MCC Directors (Workstation Satellites). All MCC System files
have to be located in MCC_COMMON (i.e. MCC_PTB_PARSER.BPT), or the user runs
into the problem, that there can be different MCC System information on the
Cluster available. That means i.e. each Satellite with DECmcc has its own
Parse Table, so you have to install a MM on each Satellite.
Uwe
|