[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

1583.0. "ALL-IN-1 and RDB" by NCBOOT::HARRIS (oooppps) Thu Oct 08 1992 19:45

    Back at the fall DECUS of 1991, my customer was told the following. And
    now that we have ALL-IN-1 3.0 , he was wondering if this is relly
    possible.  If it is, what changes do I need to make to the entry form
    invovled?
    
    The original problem is that the data for the corp phone directory is
    pulled from an indexed-sequential file with duplicate keys. This
    problem will not go away (he was told) but a workaround would be to
    make the file an RDB db. As ALL-IN-1 3.0 would be able to access RDB
    db.
    
    Is this still true?  Can ALl-IN-1 3.0 access RDB db's?
    
    thanks - ann
T.RTitleUserPersonal
Name		DateLines
1583.1GIDDAY::SETHIMan from DownunderFri Oct 09 1992 08:2016
    Hi Ann,
    
    I know there is an asset call SRA (SQL Relational database Access) for
    version 2.4 of ALL-IN-1.  This provided the interface between ALL-IN-1
    and Rdb.
    
    I have been looking around Version 3.0 and cannot find anything.
    
    >This problem will not go away (he was told) but a workaround would be to
    >make the file an RDB db. As ALL-IN-1 3.0 would be able to access RDB db.
    
    Can you tell me what is the problem ?  
    
    Have a good weekend
    
    Sunil
1583.2Mysteries of our time?SCOTTC::MARSHALLDo you feel lucky?Fri Oct 09 1992 09:456
Hi,

To my knowledge, there is nothing officially in the base product to support
RDB databases.  I wonder who said there would be, and what they had in mind?

Scott
1583.3Never trust an Engineer at DECUS :-)IOSG::PYEGraham - ALL-IN-1 Sorcerer's ApprenticeFri Oct 09 1992 10:2010
    There was some speculation about including SRA support at one time, but
    due to too many other things to do, it never got implemented. I'm sure
    the customer understands that anything he was told by an Engineer at
    DECUS is only idle rumour and speculation :-)
    
    There is of course the Data Decide functionality allowing ENTRY forms
    to have their data mapped to something entirely different, which could
    be a program providing access to RDb.
    
    Graham
1583.4Rdb/VMS and ALL-IN-1: SRA is the way to goSIOG::T_REDMONDThoughts of an Idle MindFri Oct 09 1992 11:3417
    SRA is not an ASSET any longer. It's one of these "Digital Strategic
    Applications" (DSA), I think.  My group looks after SRA (with great
    loving care) since Charlotte went away.
    
    Basically SRA allows you to map a relation within an Rdb/VMS database
    via an ENTRY form.  It uses ALL-IN-1 V3.0's Data Decide facility to do
    this. Kits are available for V2.4 and V3.0 (the V2.4 kit uses a
    slightly different implementation).  You can play with the data via the
    form just like any other file. You would be able to implement a phone
    directory (or anything else) in a database via SRA.  The product also
    allows read-only access to Oracle and DB2 databases, though you need
    some extra software to allow this to happen.
    
    A notes conference is available on ASIAGO::SRA.  Press KP7 to add the
    conference to your notebook.
    
    Tony
1583.5data decide ?NCBOOT::HARRISooopppsFri Oct 09 1992 19:226
    thanks for the suggestions!
    
    i've passed them on to the customer.  just 1 question though, what is
    DATA DECIDE?  haven't found anything on this yet in the 3.0 doc set.
    
    	ann
1583.6Qualifier to .FILEIOSG::PYEGraham - ALL-IN-1 Sorcerer's ApprenticeSat Oct 10 1992 12:307
    I'm not sure where, if at all, it's documented, but it's a new
    qualifier to the .FILE directive in an entry form.
    
    Someone cleverer than me will be able to tell you if it's not in the
    FM.
    
    Graham