Conference iosg::all-in-1_v30

    
    Hi TK,
    
    One thing which comes up is that you're using one of the 15 paramaters
    on the second screen. These are only needed if you're using Syntax 1.
    Syntax 1 means a function which routine(s) can handle the new
    Centralized Parsing. Syntax 2 is defined for functions which use
    routines based on V2.* syntax. If BASISplus has been modified for V3.0
    and uses the Centralized Parser then use Syntax 1, but if you're
    working with an old BASISplus (V2.* compatible), use Syntax 2 without
    parameters.
    
    > Syntax 1 Riutine address:
    > Syntax 2 routine address:       oac$idi_basis
    >
    > Generic:                        N (this may be ok since BASIS
    >                                    is declared as a syntax 1
    >                                    type. Nevertheless I also
    >                                    tried 'Y' as well)
    
    You confuse me here. Is it or isn't it defined as Syntax 1?
    
    The 'Foreground only' indicates whether or not the function works from
    within the Script Symbiont ('N' means it will).
    
    Please check with IDI whether or not BASISplus should use Syntax 1.
    
    Ciao,
    
    	Simon

    Hi Simon,
    
    Thanks for the prompt reply.
    
    Sorry, Some typos have crept into in my .0; It is in fact syntax 2. 
    Also I typed 'scripts' where I meant 'a1trace.log'.
    
    The values were as given by IDI after I had tried my own. I had also
    tried various combinations including one with no parameters. I
    understand that ALL-IN-1 parses the command line only if it is of
    syntax 1; (just to make sure I tried this too, when ALL-IN-1 itself 
    complains about the syntax not being right).
    
    From a1trace.log I can find that the BASIS function is passed with 
    appropriate keyword and parameters. However BASIS replies with the 
    error message 'invalid or insufficient number of parameters'.
    
    regards -tk
    
    

    
    I've seen something like this before (remember Caroline?)
    
    How are you calling your functions.
    If no parameters are required then you need to put () after your
    function I believe.  If paramters are required don't forget the
    brackets.
    
    Let me know,
    
    Ta,
    
    Mike

    
    Hi TK,
    
    As I understand the OAC$IDI_BASIS is still of what we call an old type
    syntax, I'm almost sure you can just take the defaults of what the
    OA$SCT$SDF offers:
    
    ----------------------------------------------------------------
    Function name: BASIS
    
    Application: OA
    
    Syntax 1 routine address: 
    Syntax 2 routine address: OAC$IDI_BASIS
    
    Return value type:                mechanism:
    
    Invisible:        N         Generic:         N
    Untrimmed result: N         Foreground only: N
    
    Parameter count:    0
    
    Parameter list address:
    Keyword table address:
    ---------------------------------------------------------------
    
    This is what basically got defined in the former OASDF.BLI. The only
    important additional field is 'Invisible:'. The other field become
    important with the new syntax definitions.
    
    Ciao,
    
    	Simon
    

    RE.1
    
    > BOUGHT TEAMlinks WHICH NEEDS V3.0. 
    
    You can use TeamLinks with 2.4 through TCP (TeamLinks Connection
    Package).
    
    Jan

    The last time I talked to BASIS they were using 'old-style-syntax'
    (this was during FT of course) - I wonder if they got confused
    when the syntaxes (GAP please correct the plural I know you will)
    were renamed and swapped around. They were even still reading the old
    BL90 documentation.
    
    Interestingly the contact at IDI was one George Florentine who of
    course used to work for DEC on the FileCabServer (when it was called
    DSMS and/or the Index Server)
    
    Sounds like they need to go on Tony's course (:==:)
    
    Jan's comments about TeamLinks are of course true but unfortunately
    the marketing blurb on all this seems to misleading (See A1INFO and
    WINDOWS_OFFICE for lots on this) to everyone.
    
    Regards,
    
    Andrew.D.Wicks
                                                 

    Thanks Simon, Andrew and others and sorry for the late acknowledgement.
    
    The problem was IDI had supplied a patch which replaced a module each
    in two of the BASIS .OLB's. BASISplus was not linked with this new
    .OLB's due to an oversight on part of the customer. When I linked
    ALL-IN-1, it took the new .OLB (through sitelink.com) and the resulting
    OA$MAIN.EXE was not compatible with old BASIS server image.
    
    Thanks and regards! tk