Conference iosg::all-in-1_v30

    I have some information on SDFs for V3.0. I'll see if I can find it
    online somewhere. Basically it's a very simple process.
    
    1. Select the OA$SCT$SDF/OASDF element from the CM Access Base 
       Elements menu.  This is the data file where SDFs are now declared.
    
    2. Copy the element to the development area.
    
    3. Edit OA$SCT$SDF. Make one entry (via an INDEX form) for each 
       SDF stating the name and its entry point (address).
    
    4. Press F10 to exit. CM asks do you want to keep the changes. 
       Answer Y.
    
    5. Mark the element to be moved into the live area. CM merges the
       contents of OA$SCT$SDF through a boilerplate and creates some
       MACRO code. This is then assembled to create a .OBJ.
    
    6. The maintainer processes the ML request. CM then moves the .OBJ
       into OA$SITE_BUILD_SHARE:SITEOALIBR.OLB.
    
    7. Amend SITELINK30.COM (using CM of course) to add references to the
       modules containing the actual code for the SDFs.
    
    8. Move SITELINK30.COM into OA$SITE_BUILD_SHARE
    
    9. Relink ALL-IN-1.
    
    10. Test the new image.
    
    Easy...
    
    Tony

    
    Darryl,
    
    I don't know if the Field Test documentation described the difference
    between Syntax 1 & 2, but in case make sure that when SDFs are created
    make sure Syntax 1 is used for the new (Centralized Parser) code and
    Syntax 2 for old-type code.
    
    Ciao,
    
    	Simon

    Thanks all!
    
    But I think the customer also wants that describes internal routines in
    ALL-IN-1.  He has attended the programmer II course but would like
    something more in-depth, if that's possible.  They are heavily
    customized here and would like to use as much of the internal code as
    possible so that they don't have to write something that is already
    there.
    
    Darryl

    Darryl,
    
    The old Field Test notesfile had a very long discussion in two separate
    notes (83 was one of them) about how 'simple' it is to add SDFs in v3.0 
    so you might be able to have a look in there but Tony has summarised it.
    
    I'd disagree (but then wouldn't I?) about the location of SITELINK30
    in that I have and would put it into OA$SITE_BUILD_ENGLISH as opposed
    to SHARE on the basis that A1LINK lives in OA$BUILD_ENGLISH and if
    customised (e.g by WPCORP) would live in OA$SITE_BUILD_ENGLISH.
    
    Depending on how old your documentation is you may find the following
    translations useful:
    Old-style syntax --> Syntax style 2
    New-style syntax --> Syntax style 1
    (I knew my FT1 doc-set would come in use sometime!)
    
    Regards,
    
    Andrew.D.Wicks
                         

    Re .3,        
     
    Sounds like another advert for "Tony's class" in August is called for.
    
    REgards,
    
    Andrew.D.Wicks

    He plans to go to the Tech Update course but would like some in-depth
    info now.
    
    
    Darryl

    Which Tech Update is the customer attending?  The only V3.0 seminar
    that I believe covers CLI at all is the Advanced Technical Seminar in
    August. We spend a whole day on the ins and outs of CLI under V3.0..
    
    Tony

	RE: .3

�    But I think the customer also wants that describes internal routines in
�    ALL-IN-1.  He has attended the programmer II course but would like
�    something more in-depth, if that's possible.  They are heavily
�    customized here and would like to use as much of the internal code as
�    possible so that they don't have to write something that is already
�    there.

	We used to provide two levels of training on internal code:  one for
specialists, which included many of the common facilities (OASTR, OADATE,
OADB, OACMD, OAMSG, OASYM, OATRA, etc.) that might contain useful routines that
could be used in integrating other applications; and one for customers, which
only described some of the very top-level routines (e.g., OACMD, OASYM).  The
point is (and I think Engineering will agree with me) that we can't really go
too far in documenting/supporting existing internal routines, not only because 
of the increased support issues, but also because it can "hamstring" future
development.

	It's already enough of a problem that we must constantly be backward-
compatible at the API level -- thereby continuing to support old functions, old
syntax, etc.  We don't need to add to our troubles by having to do that at the
internal level as well.

	Yes, the AP II course does point out that Site Defined Functions *can*
invoke any internal code -- if you know about it.  But I really think that the
only thing we typically "support" is the idea of calling OA$CMD_DISPATCH, or
something equally simple.

	F

    We actually do still teach a Code Level Integration class, at least in
    Europe. It has been updated for V3.0, but I don't know when we will be
    teaching it next. Would your customer like to fly over?
    
    Tony

    RE: .9
    I'm sure he would love to fly over and so would I but I think we would
    both have the same problem:  no one to pay for us to fly over.
    
    Any chance of getting it taught over here?  I'm sure you could fill the
    class!
    
    RE: 8,
    The customer pointed out to me the following:
    	Under the chapter Intergrating an External Application, page 24-22,
    section 24.6; CONTACT YOUR DIGITAL SUPPORT CENTER IF YOU WANT TO MAKE
    USE OF ALL-IN-1 INTERNAL ROUTINES.
    
    Does this mean that he can call the CSC and get the information that he
    wants and if so, how come we can't get it here?
    
    
    Darryl

    Darryl,
    
    Your customer is more alert than most the entry on page 24-22 is not
    the only one that encourages you to "contact your local support center"
    as there is one also at the bottom of page 24-23 that encourages you
    do the same if you'd like to add new source code elements and there's
    also one back on page 24-17 that says that the CSC knows how to add
    SDFs with more than 15 parameters.
    
    I'm sure there's someone out there who knows how to do these operations
    but they don't appear to be at this CSC at the moment and the info
    doesn't appear to be in STARS either.
    
    Obviously whoever wrote chapter 24 of the APR guide either bore some
    long standing grudge against the CSCs or was just trying to see whether
    we were intelligent enough to figure out the answers since the phrase
    "contact your local CSC"  does not seem to appear in any other chapter
    of any other book (:==:)
    
    When you work it out please give me a call and let me know just in case
    soemeone else wants to do it.
    
    Regards,
    
    Andrew.D.Wicks

    We can certainly arrange for a class to be taught on-site. Send me mail
    if you want to pursue this further. Depending on the number of people
    to be trained, this can be a cost-effective way of getting this
    knowledge.
    
    The customer can, of course, call the CSC. But I suspect that a course
    in CLI programming will be very boring if delivered over the phone.
    Won't your ear start hurting after an hour or so?
    
    Tony

    RE: 12
    
    Tony, 
    
    I was thinking about a class that was not on-site so everyone would be
    able to come; plus there would be only two of my customers  who could
    attend.  Ani I still think you could fill this class without any
    problem.
    
    As for getting the CLI class over the phone; I'm sure I could find me a
    speaker phone.  ;-)
    
    Darryl
    

    If there is enough interest in the U.S. to fill a CLI class I don't see
    any reason why it can't be offered by either ourselves or perhaps the
    folks in Charlotte. You can help by asking your local ES people to
    arrange it. They can contact me to set up trainers and dates.
    
    Tony