| 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 |
I'm trying to customize a message in OAMESS.MSG, in ALL-IN-1 3.0: I did
it in version 2.3, and Im trying to do same things with this version,
but it doesn't work.
What I did in 2.3 was:
- modify message in oamess
- compile message file to object without text
- replace in OA$BUILD_SHARE:OALIBR
- compile message file to object with text
- replace in OA$LLV:OALLV
- relink ALL-IN-1
What's new in this version?
Thanks in advance.
Paola Negro
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1757.1 | Adding messages in V3.0 | IOSG::BILSBOROUGH | Just testing. Please ignore!!! | Wed Nov 11 1992 16:08 | 27 |
CM (Customisation Management)
ABE (Access Base Elements)
SEL
element SITEOA type A1MSG
CO (Copy to development)
Exit screen to CM main menu
Edit the SITEOA A1MSG file and add the symbols
MLA (Mark for moving to live)
AM (Application Maintainer)
PME (Process marked elements)
Enter SITEOA as the element and press return
Enter ML (Move element to live)
And that's it.
HTH,
Mike
| |||||
| 1757.2 | CM doesn't do everything yet! | AIMTEC::WICKS_A | Liverpool 4 Norwich 1 | Wed Nov 11 1992 17:16 | 21 |
Re .1
Mike sorry but that's not necessarily true!
CM in v3.0 only supports customisation of the new .A1$MSG files that
contain messages that used to be in OASYMMSG.MAR.
Any messages that are in VMS message files (.MSG extension) still
need to be customised by hand aT DCL level as they were in previous
releases and OAMESS.MSG falls into this category - this applies
to all messages called from code-level I believe.
I don't see off hand why what Paolo is doing doesn't work if he really
is changing a code-level message that is.
regards,
Andrew.D.Wicks
The procedure that the
| |||||
| 1757.3 | SITE Versions too.... | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Wed Nov 11 1992 18:02 | 15 |
You need to update the site versions of the object liobraries too,
which are searched first unless you tell A1LINK to do a "/NOCUSTOM"
link with an option I've forgotten.
$ dir oa$build:site*.olb
Directory DISC:[ALLIN1.SITE.SOURCES_ENGLISH]
SITEOALLV.OLB 506 25-OCT-1992
Directory DISC:[ALLIN1.SITE.SOURCES_SHARE]
SITEOALIBR.OLB 859 25-OCT-1992
Graham
| |||||
| 1757.4 | A recap... | CESARE::EIJS | All in 1 Piece | Wed Nov 11 1992 18:59 | 41 |
Hi Paola,
Re .0)
So, combining all the previous replies, do:
- copy oamess.msg to oa$site_build_<language> ! For insiders, yes,
! I use 'language',
! but it's late already
- modify message in copied oamess
- compile message file to object without text
- replace in OA$SITE_BUILD_SHARE:SITEOALIBR.OLB
- compile message file to object with text
- replace in OA$SITE_BUILD_<language>:SITEOALLV
- relink ALL-IN-1
(by default it will take your modifications,
specified with 'Options N' (Re .3) links without modifications)
Re .1)
> element SITEOA type A1MSG
Element is called SITE$OA type A1MSG
> Enter ML (Move element to live)
>
> And that's it.
No, the Application Manager should compile the message file via the
options SM CSZ CMF.
Ciao,
Simon
PS Who looks picky, is picky, but just to set information straight (and just
to remind Mike he owes me... ;-)
| |||||
| 1757.5 | Thanks | ROM01::NEGRO | Paola Negro EIS-Swas Roma | Thu Nov 12 1992 12:48 | 1 |