[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

4136.0. "Question about TXL and element placement..." by TAV02::CHAIM (Semper ubi Sub ubi .....) Thu May 05 1994 08:12

A customer had created a DO script file which issues a MERGE command via a BLP
file.

During the developement stage this worked fine. 

When he moved it to LIVE, it stopped working. Using DEBUG I could see that the
MERGE was never actually executed.

My investigation of the problem discovered that the DO script was placed in the
oa$site_lib_share area, which is NOT compuiled as part of the TXL, while the
BLP was placed in the oa$site_blp_share area, which is compiled as part of the
TXL. After I moved the BLP to the oa$site_lib_share area as well, all worked
fine.

Is this a known restriction.

Thanks,

Cb.
T.RTitleUserPersonal
Name		DateLines
4136.1Line > 512 bytes ...TAV02::CHAIMSemper ubi Sub ubi .....Thu May 05 1994 09:349
After further investigation, the problem may not have been the mixture of a
script not in the TXL while the BLP is in the TXL, but rather it appears that
the specific BLP has a "logical" line which exceeds 512 characters (which I
recall is an old limitation for the TXL compiler). However, in this case I
would have expected to receive some sort of error or even an access violation.

Thanks,

Cb.
4136.3Line too long errorIOSG::MAURICESix Programmers in search of an analystThu May 05 1994 10:4813
    Hi,
    
    In V3.1 there is now a check in TXL compilation for boilerplates with
    "logical" lines that exceed 512 characters, since it does cause
    problems. It usually causes an ACCVIO but it can instead result in
    memory corruption with unpredictable results.
    
    So the fix is to spilt you logical line up into lines, each smaller
    than 512.
    
    HTH
    
    Stuart
4136.4To BE or NOT to BE ...TAV02::CHAIMSemper ubi Sub ubi .....Thu May 05 1994 11:5823
My question was; is their a restriction stating that if a DO script issues a
MERGE function with a BLP and the BLP file is in oa$blp (which means that it
gets compiled within the TXL), that the DO script MUST also be compiled in the
TXL. In my specific case the DO script was in oa$lib. I chose to move the BLP
file to oa$lib as well.

Now, as I mentioned in my own reply to this note, I subsequently noticed that
the BLP file contains a "logical" line greater than 512 characters. I recall
that in previous versions there was a restriction of a maximum of 512
characters for any given line for TXL complilation. 

At this point, I don't know for which reason moving the BLP to oa$lib worked;
because of the restriction regarding the maximum line for TXL or because of a
different restriction that both the BLP and the script referrencing it must
either both BE in the TXL or both NOT BE in the TXL, but one in the TXL and one
not in the TXL won't work.

Thanks,

Cb.
4136.5It doesn't seem very likely!IOSG::PYEGraham - ALL-IN-1 Sorcerer's ApprenticeFri May 06 1994 18:015
    I wouldn't have thought so. Is there some problem with the script or
    BLP specifiying OA$LIB or OA$BLP explicitly? Or perhaps something funny
    happening with TXL search order or File Search order?
    
    Graham