[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
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 |
3084.0. "INVOKING / LINKING PROBLEM" by TOSSUC::TOTA () Thu Jul 29 1993 13:02
Hi,
I've a strange behaviour invoking ALL-IN-1 2.4 .
CUSTOMER ENVIRONMENT : ALL-IN-1 V2.4 with SRA asset installed.
Customer have ALL-IN-1 2.4 installed on
two different environments:
cluster A ( ALL-IN-1, SRA, WORDPERFECT
standalone )
cluster B ( ALL-IN-1 )
When problem appeared: Installing RDB v4.1 on cluster A
---------
it seems to be a mandatory step to
relink ALL-IN-1 to let SRA available.
Trying to relink problem appeared.
Checking on SRA conference we solve
the problem without relink ALL-IN-1.
Problem: Trying to relink customer noticed that
EACH new linked OA$MAIN image doesn't work.
In other words, customer is working with
a OA$MAIN image but isn't able to link
a new OA$MAIN image correctly working.
In details invoking ALL-IN-1 ,
main menu appears but it doesn't accept any choice,
---------------------------------------------------
repositioning cursor on the initial place if
a choice had been made.
The only thing to do is to exit with a
CONTROL/Y.
The only strange message is
"obsolete CMTXL , please recompile",
after displaying main menu.
Other details: - main menu display correctly main2 form
with "NEXT" choice
- setting another form as the first
displayed , ALL-IN-1 does't change,
it EVERY DISPLAYS MAIN MENU form as the
first one.
MY idea : It seems to be an initialization problem.
I think it's related to SET_MENU function
that set default menu.
WHY I'M confused: Customer experienced problem try to RELINK
ALL-IN-1 on cluster A.
Now,
- if I link the new image on cluster A it
doesn't work but WORKS if copied on
cluster B.
- if I link the new image on cluster B it
works but DOESN'T WORK if copied on
cluster A.
In other words , all new linked images
works on cluster B and doesn't work on
cluster A.
It seems to be either an
"environment" problem (no new image
working on cluster A ) or
a "source code" problem ( the old image
, however, works ok ).
Questions: any ideas?
In which initialization phase is there
a call to SET_MENU function?
Thanks in advance and regards,
Ivo Tota - C.S. TURIN, ITALY -
T.R | Title | User | Personal Name | Date | Lines |
---|
3084.1 | Could be caused by 2.0 update patch | ZPOVC::CHINGYUE | | Thu Jul 29 1993 16:01 | 20 |
| Ivo,
Is ALL-IN-1 2.0 update installed on cluster A ?
( ty oa$build:a1*configuration.dat )
If yes, I've got the feeling that post-installation for the patch
wasn't completed successfully, leading to a 'broken' image.
(had a similar case last month)
A simple way out would be to DE-INSTALL the patch.
(Instruction in the release note)
The only reason I could think of why it work on cluster B is that
cluster B doesn't have the update patch installed.
Reason being that the patch modified the Command table such that it
doesn't understand the 'old' .FLCs
Hope your case is just like mine. Took me 3 days to figure that out.
Best of luck,
ching-U
|
3084.2 | Sounds like known K603 prob | AIMTEC::WICKS_A | U.S.A 2 England 0 - I was there! | Thu Jul 29 1993 18:14 | 11 |
| Ivo,
Assuming that you relink is clean then the 'can't get off main menu'
is indeed caused by the patch. Delete all your .FLCs (from OA$LIB)
and try again. If that does it you can recompile them from inside
ALL-IN-1 (excepte MEMRES) - make sure that you have the NEW OA$MAIN
installed at this point.
Regards,
Andrew.D.Wicks
|
3084.4 | Feedbacks... | TOSSUB::TOTA | | Mon Aug 09 1993 09:28 | 26 |
|
Hi,
I went to the customer, last week and did some trys.
To link a working OA$MAIN image we've to deinstall K603.
I tryed to deinstall/install k603 but nothing changed.
Of course I precompiled forms libraries.
In my opinion maybe an incompatibility between
SRA and K603.
I've no other way to explain this behaviour.
Thanks another time for your help
Ivo
|