[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

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

90.0. "Customized Message files in ALL-IN-1 V3.0" by GLOVES::ALLERTON (Steve Allerton 343-0205) Tue Feb 25 1992 07:45

    
    While Im aware of the V3 changes applied to Message Symbol files 
    (i.e. the somewhat unconventional support provided in CM+) I was 
    unable to provide a confident answer posed in a class Im teaching 
    this week:
    
    A customer has in the past developed customized applications that 
    incorporate customized message symbols (in OAMESS.MSG), each with 
    a prefix associated with the application from which it is called.
    
    If the customer is to continue with this practice in V3 of ALL-IN-1, 
    will they have to continue using prior practices (manual compile) 
    (and image relink) or is there a way to have the new CM-driven 
    approach incorporate prefixes of the customers choosing?
    
    Thanks,
    
    Steve
T.RTitleUserPersonal
Name		DateLines
90.1Only a set of prefixes supported.CESARE::EIJSAll in 1 PieceTue Feb 25 1992 08:5930
    
    Hi Steve,
    
    You mean, the customer was using symbols like:
    
    	OA$_APP1_SYMBOL
    	OA$_APP2_SYMBOL
    
    or:
    
    	APP1$_SYMBOL
    	APP2$_SYMBOL?
    
    In case of 1, the same can be done in V3.0, using the SITEOA.A1$MSG,
    which can be compiled and installed from the CM menu, without
    relinking ALL-IN-1.
    
    In case of 2, the new message facility doesn't allow this. The current
    prefixes are limited to ARC, CBI, CM, DIR, EM, FC, GS, KEY, NOTES, OA,
    SA, SM, TM and WPL (look at the different message files available).
    OAMESS.MSG is now only used for CLI messages (I'll be corrected here if
    I'm wrong). So, if the customer wants to continue with his own
    prefixes, probably OAMESS.MSG (or any other MESSAGE message file) is
    the only way to do it. However, CM doesn't offer support for .MSG files
    (yet). Although adding support for it still doesn't releave him from
    relinking ALL-IN-1.
    
    Ciao,
    
    	Simon
90.2APP$ it isGLOVES::ALLERTONSteve Allerton 343-0205Tue Feb 25 1992 11:546
    
    Thanks Simon.
    
    (Again).  
    
    Steve
90.3A random comparisonAIMTEC::WICKS_AVote Bill'n'Opus for a weirder USATue Feb 25 1992 16:5326
    Steve,
    
    Well i'm glad you were confused also because i've tried at least around
    here to explain the difference between Message Files and Message Symbol
    Files and failed spectacularly - hopefully customers will understand.
    
    And here is Simon's chance to correct me:
    the differences between the two.
    
                            	MSG		.A1$MSG
    			        ===		=======
    Uses VMS message utility    Yes		No
    Supported by CM+            No		Yes
    Requires a relink		Yes		No
    Installed as Global Sects	No		Yes
    Resides in a VMS .OLB	Yes		No
    
    So for .MSG files such as MAIL, OAMESS, OASAMESS it's business as
    usual, except it would appear that we've lost the section that used
    to be in the Management Guide that told people how to customize them.
    
    
    Regards,
    
    Andrew.D.Wicks
90.4Comparison is correctCESARE::EIJSAll in 1 PieceThu Feb 27 1992 12:399
    Hi Andrew,
    
    You didn't give me much of a chance, did you?... ;-). It's all
    correct.
    
    Ciao,
    
         Simon