[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

288.0. "Source Code Tables??" by KERNEL::HOULDINGJ (Jill Houlding - Back in Basingstoke) Fri Mar 20 1992 09:51

	Hi

	I am preparing an overview of CM to deliver as part of a training course
	and I have been looking at the new element types in ALL-IN-1 V3.0. I 
	cannot find any description of what a source code table is nor any such 
	element in a standard system. I think these might be something to do 
	with the table of functions held in OACTL.BLI???

	Please can someone explain what these source code tables are and the 
	difference between the OASCT and SCT.
	
	
	Thanks

	Jill 
T.RTitleUserPersonal
Name
DateLines
288.1PAJERO::RHOTONJohn Rhoton @TNO - DTN 871.7947Fri Mar 20 1992 11:0224
Source code tables are ALL-IN-1 data files, mapped by entry forms, which
contain information that is converted to code and linked with the ALL-IN-1
image.  At present (ALL-IN-1 V3.0) there are source code tables for
site-defined functions (previously in OASDF) and special symbols (previously
in OAGBL).  Site-defined functions are a specific case of source-code
tables for reasons I will ignore for the moment.  They therefore use
their own CM elements SDF and OASDF rather than SCT and OASCT.

The difference between SCT and OASCT (and also between SDF and OASDF) is
whether the object module is replaced in the OALIBR object library when
it is moved to live.  Unless you are inventing your own tables you will
be using OA*.

Just to give you an idea of how these work:  The entry form manages the
records in the data file and ensures alphabetical ordering, uppercasing
etcetera.  When the element is moved to live a boilerplate processes
the datafile and produces an intermediate VAX MACRO file which defines
the table structure and contents.  The MACRO file is assembled and then
optionally replaced in the object library as mentioned above.  You still
need to relink the main image manually for the changes to take effect.

I hope this helps,

John
288.2Also earlier here...IOSG::PYEGraham - ALL-IN-1 Sorcerer's ApprenticeFri Mar 20 1992 11:594
    I'm sure there's been some recent discussion about this here too, but I
    can't find it with a casual glance.
    
    Graham
288.3You too??AIMTEC::WICKS_AVote Bill'n'Opus for a weirder USAFri Mar 20 1992 16:1312
    Jill,
    
    So you're doing training on CM as well?? 
    
    Just as soon as I have my stuff sanity checked by Simon Eijs
    i'll let you have a copy. There's lots of stuff about element types 
    such OASCT and OASDF (I haven't done SCT and SDF yet) and all the other
    new and sexy stuff to do with Message Files and Symbols.
    
    Regards,
    
    Andrew.D.Wicks
288.4ThanksKERNEL::HOULDINGJJill Houlding - Back in BasingstokeFri Mar 20 1992 16:5019
Thanks all for the assistance.

Andy,

The training that I am giving is at a fairly superficial level (at 
least this time...). I am including a section on CM in the Installation 
course which I am delivering in the UK next week just so the guys doing 
the Installation have some understanding of how it has changed.

I would be interested to see your materials as I may well have to do some 
more in-depth stuff later.

Thanks again

Cheers

Jill

P.S Where is the stuff on SCT and OASCT documented - I couldn't find it! 
288.5Look for it in the INBOX laterAIMTEC::WICKS_AVote Bill'n'Opus for a weirder USAFri Mar 20 1992 17:2113
    Jill,
    
    Next week and you've already started preparing?? (:==:)
    
    SCT and SDF stuff is in APR guide Chap 24.
    
    I'll send the material in the mail later... don't forget this'll cost
    one pint of beer at Christmas!
    
    Regards,
    
    Andrew.D.wicks
                                  
288.6We will document all this soonSIOG::T_REDMONDThoughts of an Idle MindFri Mar 20 1992 22:3313
    We are quite aware that there is a subtle lack of material regarding
    some of the more esoteric corners of CM+. We hope to do something about
    it by submitting some articles for publication in the information
    update. First we have to get rid of some other bits and pieces, then we
    will start to document things like SDFs, A1MSGs, ESOs and LSOs. Not to
    mention how to package and receive elements, use of foreign files,
    adding new element types, adding new options to the context senstive
    menus etc. etc. etc.
    
    All this could easily fill a book... must start writing something some
    day...
    
    Tony