| Title: | *OLD* ALL-IN-1 (tm) Support Conference |
| Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
| Moderator: | IOSG::PYE |
| Created: | Thu Jan 30 1992 |
| Last Modified: | Tue Jan 23 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4343 |
| Total number of notes: | 18308 |
Yo,
I need to know how to get my old TPU section to work on our
just-upgraded ALL-IN-1 V3.0 system. Previously, we had the OATPU
integration in place and all I had to do was define a logical and life
was groovy. Now the default EVE section is forced upon me and I'd like
to "augment" it with things from my old section file.
What do I do?
athanks,
douglas
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 932.1 | And Yo to you too | AIMTEC::WICKS_A | DEC Mail Works for ME sometimes | Thu Jun 25 1992 16:55 | 31 |
Douglas me old mate here's the answer from our friends in Engineering
to this one:
PROBLEM:
When TPU is ALL-IN-1 editor previously defined section file (TPU$SECTION)
is not used.
ANALYSIS:
Create an EVE section file and define the logical TPU$SECTION to point to
it. It is used when accessed outside ALL-IN-1, but ALL-IN-1 seems not to
use the EVE section file.
SOLUTION:
\This has been reported to Engineering.
This is the correct behaviour. The section file used by ALL-IN-1 must be
used. ALL-IN-1's section file contains the callbacks to ALL-IN-1 to support
such things as UDPs and ALL-IN-1 GOLD functions. It also contains the
support to implement the security checking necessary for the ALL-IN-1
environment.
Since ALL-IN-1 needs a special section file, it deliberately ignores the
TPU$SECTION logical. Instead, it checks the OA$TPU_SECTION logical.
However, this logical *must* point to a section file that has been derived
from the original ALL-IN-1 section file.
Regards,
Andrew.D.Wicks
| |||||
| 932.2 | Oh come on, there's got to be a way... | ANGLIN::CARLSON | Tue May 03 1994 22:02 | 9 | |
Where does the OA$TPU_SECTION logical point to?
Is there a way to overlay the original ALL-IN-1 TPU section file with
one that is more appropriate to our users?
Can we re-define the OA$TPU_SECTION logical to point to a different
keyboard mapping file per job or process without breaking ALL-IN-1?
Julie
| |||||