[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

2283.0. "what is oa$msg_get" by AIMTEC::GRENIER_J () Wed Feb 17 1993 17:59

    OA$MSG_GET - what is it?  Customer is having relink problems after
    trying to relink to include a customized module (previously written
    by Charlotte for her).  There are the following undefined symbols:
    
    	oa$_day_of_week_1
    	oa$_day_of_week_2
    	                .
                        .
                        .
	oa$_day_of_week_7
    
    	
    Her module command is:
    
    	oa$msg_get(oa$_day_of_week_1,sun);
    
    Those symbols are still used in V3.0 and we know are valid, trying
    to figure out why her module thinks they are undefined.  We cannot
    find any documentation on oa$msg_get.  Any help would be appreciated.
    
    
    Jean
T.RTitleUserPersonal
Name		DateLines
2283.1LOG file ??AIMTEC::VOLLER_IGordon (T) Gopher for PresidentWed Feb 17 1993 18:1810
    Jean,
    
    	OA$MSG_GET is a routine that is used to copy the text
    	representation of a message to a string variable.
    
    	Do you have a pointer to a log file ?
    
    Cheers,
    
    Iain
2283.2P.S I can show you the BLISS code!AIMTEC::WICKS_AWALES 10 England 9Wed Feb 17 1993 18:5320
    Jean,
    
    OA$MSG_GET is a global function that takes two arguments
    
    MSG_CODE - Longword containing the value of the Message Code
    MSG_DEST - String descriptor
    
    Returns are: Error status from $GETMSG
                 Status of the call to $FAOL
    
    This routine gets a message and stores it in MSG_DEST. The text portion
    of the message is the only thing returned. If there are more than 2
    parameters, the rest are FAO arguments. In this case, the string will
    be passed through FAO before being returned.
    
    (wonder where I copied that from)
    
    Regards,
    
    Andrew.D.Wicks
2283.3Use OA$Sym_Get_Symbol?IDNTCR::RHOTONJohn Rhoton @TNO - DTN 871.7947Thu Feb 18 1993 08:5927
>    Her module command is:
>    
>    	oa$msg_get(oa$_day_of_week_1,sun);
>    
>    Those symbols are still used in V3.0 and we know are valid, trying
>    to figure out why her module thinks they are undefined.  We cannot
>    find any documentation on oa$msg_get.  Any help would be appreciated.
    
    
    I suspect that your problem derives from the fact that most of the
    messages were moved to the new message symbols from V2.4 to V3.0.
    
    As a result you can't use OA$Msg_Get to access them but could use
    OA$Sym_Get_Symbol instead:
    
    	OA$Sym_Get_Symbol (%ASCID'oa$_day_of_week_1', sun)
    
    or something like that.
    
    Alternatively you could take the messages and put them back into a
    message file you link with the image but personally I would recommend
    the first.
    
    
    Hope this helps,
    
    John