[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | ALL-IN-1 (tm) Support Conference |
Notice: | Please spell ALL-IN-1 correctly - all CAPITALS! |
Moderator: | IOSG::PYE CE |
|
Created: | Fri Jul 01 1994 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 2716 |
Total number of notes: | 12169 |
2494.0. "EXITXOP is unknown" by TIMAMD::VICTOR () Thu Jan 30 1997 13:00
Hi,
We found a great bug in the 3.2 SPANISH ALL-IN-1 version.
All customers running ALL-IN-1 3.2 in SPANISH receive the message
Function "EXITXOP is unknown", when they press the SA option in every menu.
The TRACE lines which show the error are:
SA {CR}
![FORM] Form: MAIN, Field: CHOICE/7, Page: 1, Key Value: {CR}
![FUNC] Function: OA$FLD_DONE, Cmd line:
![A1LOG] Entry:
![FIELD] Field: CHOICE/7. All fields checked
![FIELD] Field CHOICE being post-processed. Workspace: 000C0000
![FIELD] Field: CHOICE. Returning field contents
![FORM] Form: MAIN, Field: CHOICE/7, Page: 1, Input: SA
![SYMBOL] Symbol: MAIN2, Value:
![A1LOG] Entry: %OA-I-LOGERROR, %OA-E-OAFE, La funci�n "EXITXOP" es desconocida
! , ambigua o no admitida
![SYMBOL] Symbol: OA$FULL_NAME, Value: PAM ALL-IN-1 System Manager
![PUT] Field: USER/0, Page: 1, Text: PAM ALL-IN-1 System Manager
![SYMBOL] Symbol: OA$TITLE, Value:
![SYMBOL] Symbol: OA$DAY, Value: Lunes
![PUT] Field: DAY/2, Page: 1, Text: Lun
![SYMBOL] Symbol: OA$DATE_FULL, Value: 27-Ene-1997
![PUT] Field: DATE/3, Page: 1, Text: 27-Ene-1997
![IO] Getting record from CAB$PENDING, Key: MAIL MANAGER, Key-of-ref: PENDIN
! G_KEY/0
![SYMBOL] Symbol: OA$MAIL_COUNT_DISPLAY, Value:
![FIELD] Field CHOICE being pre-processed. Workspace: 000C0000
![FIELD] Current Field: CHOICE/7
![FORM] Form: MAIN, Field: CHOICE/7, Page: 1. Getting user input
![MESS] Message: La funci�n "EXITXOP" es desconocida, ambigua o no admitida
![INPUT] Terminal input follows:
exit {CR}
![FORM] Form: MAIN, Field: CHOICE/7, Page: 1, Key Value: {CR}
![FUNC] Function: OA$FLD_DONE, Cmd line:
![A1LOG] Entry:
![FIELD] Field: CHOICE/7. All fields checked
![FIELD] Field CHOICE being post-processed. Workspace: 000C0000
![FIELD] Field: CHOICE. Returning field contents
![FORM] Form: MAIN, Field: CHOICE/7, Page: 1, Input: exit
![SYMBOL] Symbol: MAIN2, Value:
![FUNC] Function: EXIT, Cmd line:
![A1LOG] Entry:
![MESS] Message:
MANAGER se despidi� de ALL-IN-1 el 27-Ene-1997 04:
! 31pm
![FLOW] Undisplaying all workspaces
![A1LOG] Entry: %OA-I-LOGSTOP, Parando ALL-IN-1
Anybody could help us?
Regards,
Victor G.
T.R | Title | User | Personal Name | Date | Lines |
---|
2494.1 | | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Thu Jan 30 1997 14:36 | 7 |
| Normally this is caused by having two menu options translated to the
same string, so that the code adds the two bits of named data together
on the form.
I suggest you search through all the OA$BUILD:*.A1$MSG files for lines
that contain both 'MO' (Menu option) and 'SA' your problem string and
see if that reveals any clues.
|
2494.2 | Similar to V3.1 and Work. | TIMAMD::VICTOR | | Fri Jan 31 1997 09:33 | 22 |
|
Hi, Graham
We find *.A1$MSG "<MO>","<SA>" in
$1$DUA11:[ALLIN1.SOURCES_SPANISH]OA.A1$MSG;4
MO_EXIT <SA>
!BIV MO_MONTH_OVERVIEW <MO> ! TMS_MORE_PAGE2
MO_ORIGINAL <MO>
!MO_SA <SA> ! DEFAULT
But this is the same in ALL-IN-1 V3.1 Spanish version and work fine.
Can you tell me what is the version problem or what I can do
to resolve this bug.
Thanks,
Victor G.
|
2494.3 | | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Fri Jan 31 1997 09:53 | 8 |
| Perhaps the translation of EXit into SA in your language is
clashing with the SA (ADM - System Administrator) option in English.
Has the symbol for MO_SA in OA.A1$MSG been changed from SA to something
else in Spanish?
Another guess, have the symbols MO_EXIT and MO_EXIT2 in OA.A1$MSG been
translated to *different* things from each other? In English, they are
<EX> and <EXIT> and they must be different.
|
2494.4 | More info. | TIMAMD::VICTOR | | Fri Jan 31 1997 10:52 | 43 |
|
Hi, Graham
Here, there is more information,
1) $ sear *.A1$MSG "MO_EXIT"
$1$DUA11:[ALLIN1.SOURCES_SPANISH]OA.A1$MSG;4
!BIV MO_EXIT <EX> ! DEFAULT
MO_EXIT <SA>
!BIV MO_EXIT2 <EXIT> ! DEFAULT
MO_EXIT2 <EXIT>
It is different, as you can see.
2) $ sear *.A1$MSG "MO_SA"
$1$DUA11:[ALLIN1.SOURCES_SPANISH]OA.A1$MSG;4
!MO_SA <SA> ! DEFAULT
MO_SA <ASM> ! DEFAULT
| V3.1 | V3.2 |
| | |
-------------------------------------------------
ASM | ALL-IN-1 | Invalid choice|
| Administration| |
-------------------------------------------------
<FORM SA | ALL-IN-1 | ALL-IN-1 |
| Administration| Administration|
-------------------------------------------------
SA | EXIT | EXITXOP error |
-------------------------------------------------
What does this information mean?
How can we solve this problem, as it is very important, every customer
that upgrades to 3.2 is going to call very angry about this.
Regards,
Victor G.
|
2494.5 | I think I've found the problem.... | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Mon Feb 03 1997 11:24 | 25 |
| OK, I think I may have found it. On the English DEFAULT form, the menu
option SA is defined:
<FORM DEFAULT
CTRL/N
;;SA;;
XOP OA$_MO_ADMINISTRATOR
I don't think this should be there. Instead, it should be using the
symbol OA$_MO_SA from OA.A1$MSG. Actually this error is present on the
INTDEFAULT form too.
I can't find when this 'bug' was first put into the form, and I have
looked in the V3.1 and V3.2 CMS libraries. I guess that someone must
have fixed the form in the previous Spanish version.
Can you look at the named data in the previous version of the DEFAULT
form, and see what was there?
Anyway, it's a bug in the base, that you should report. I don't know
what you should do for the translated versions, whether there should be
a patch, or you can tell people how to fix it by editing the form on
their systems.
|
2494.6 | Full details of the V3.1 fix | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Tue Feb 04 1997 11:25 | 53 |
| I've spoken to the people in Israel now, and one of the mysteries has
been solved. They found the problem in V3.1 too, and fixed it in the
V3.1 kit. Unfortunately, the fix didn't get into either the V3.2 base
code (for it is a base bug!) nor was the fix reapplied to the V3.2
translated versions.
Sorry!!
When changing the DEFAULT form, the V3.1 fix also changed the following
lines:
************
File V31_DEFAULT.FLX;1
136 FORM INTMENU/PRE='.IF OA$MENU_CHOICE == OA$_MO_TIME THEN -
137 GET OA$DISPLAY = OA$_APP_OTHINTSES\\TIME -
******
File TRANSLATED_DEFAULT.FLX;1
136 FORM INTMENU/PRE='.IF OA$MENU_CHOICE == OA$_MO_TIME OR -
137 OA$MENU_CHOICE == SM$_MO_TIME THEN -
138 GET OA$DISPLAY = OA$_APP_OTHINTSES\\TIME -
************
************
File V31_DEFAULT.FLX;1
294 ;;OA$_MO_WORD_PROCESSING;;
******
File TRANSLATED_DEFAULT.FLX;1
295 ;;SM$_MO_TIME;;
296
297 TIME
298
299 ;;OA$_MO_WORD_PROCESSING;;
************
************
File V31_DEFAULT.FLX;1
441 ;;SA;;
******
File TRANSLATED_DEFAULT.FLX;1
446 ;;OA$_MO_SA;;
************
************
File V31_DEFAULT.FLX;1
450 ;;SM;;
******
File TRANSLATED_DEFAULT.FLX;1
455 ;;OA$_MO_SM;;
************
************
File V31_DEFAULT.FLX;1
703 ;;CM$_MO_CUSTOM_MANAG;;
******
File TRANSLATED_DEFAULT.FLX;1
708 ;;OA$_MO_CUSTOM_MANAG;;
************
|