[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

1274.0. "CM: MLA moves even with compile error" by LEMAN::PUNKIE::REGINA (Carrie's in the carrot land) Wed Aug 19 1992 17:56

I had to make a code level integration for OAGBL share (IOS V3.0).
The compile did not work as one of the required files (LIB.L32) 
was missing.

The point is that the DCL compiler error message flashes by, leaves you 
with a clean ALL-IN-1 screen, makes the element status "Move pending"
and there you sit with an old version without necessarily realizing it
(immediately) when you did not sit in front of the MLA watching it.

I would expect the compile to abort the MLA action and come back with
an error message. 

/rhr
T.RTitleUserPersonal
Name		DateLines
1274.1Which one out of interestAIMTEC::WICKS_AIt wasn't supposed to end this wayWed Aug 19 1992 18:4612
    Regina,
    
    Which part of OAGBL did you need to modify. One of the central ideas
    of v3.0 was to eliminate the need to change OAGBL and OASDF which I
    think has been achieved to a large degree. If there are still tables in
    there (such as OA$MAIDES) that are going to be customised then it would
    be best to let Engineering (CM and IOSG) know so that they can consider
    whether they can make them Source Code Tables in a PFR
    
    Regards,
                                                                  
    Andrew.D.Wicks
1274.2Already known, thanksIOSG::BILSBOROUGHJust testing. Please ignore!!! Thu Aug 20 1992 01:400
1274.6Given the speed ...LEMAN::REGINACarrie's in the carrot landThu Aug 20 1992 15:119
    Well,
    
    The application adds a line to the MAILFUN part.
    
    It just took me 1 hour on a 6000-400 to compile OAGBL. From that point
    of view, yes it would be desireable to have something 'faster'
    to do code level integrations!
     
    /rhr                             


1274.8OAGBL is really quick now....IOSG::PYEGraham - ALL-IN-1 Sorcerer's ApprenticeThu Aug 20 1992 21:219
    Regina,
    
    Er, yes, a reorganisation of our include files in V3.0 had the
    unfortunate side effect of making OAGBL rather slower to compile. Look
    on the bright side, at one time during V3.0 development, it took over
    *SIX* hours to compile. Understand that this causes us rather more
    frequent grief than you, so might get looked at. Meanwhile, sorry...
    
    Graham


1274.10OAGBL needs Bliss V4.6LEMAN::REGINACarrie's in the carrot landFri Aug 21 1992 11:017
    By the way: I had to install Bliss V4.6 in order to be able to
    compile OAGBL. I never had grief with OASDF. The L32 that come
    with the kit are compiled with T4.6.
    
    Just a word of warning. (Haven't seen Bliss32 V4.6 as prereq)
    /rhr