DSXchange

RT_LOGxxx has a multi value column MSG.TEXT with output depth of 60T.

What would be the maximum length between two value marks? This is required to determine FMT format value to get the text in one line without any breaks.

Below statement works as expected when number of characters before the first value mark are less than 100 but fails when it exceeds. So I would like to know what value we can use for FMT so that irrespective of length all the TEXT is displayed in one line?

SELECT EVAL "FIELD(MSG.TEXT,CHAR(253),1)" AS EVENT FMT '100L' FROM RT_LOGxxx

There are no limits. The original UniVerse database storage concept allowed for completely arbitrary stucture sizes (limited only by machine resources).

Some log messages, particularly those returned from Microsoft ODBC data sources, are thousands of characters long.

Thank you Ray!
I am not a premium member but planning to be one very soon. Would you mind suggesting the alternative for my requirement so that below sql works without any line breaks for each row it returns irrespective of log message length.

SELECT EVAL "FIELD(MSG.TEXT,CHAR(253),1)" AS EVENT FMT '100L' FROM RT_LOGxxx

Please help me out! I really appreciate it!

Your are using "FMT '100L'" in your command, so if you have more than 100 characters the SELECT inserts a line break. It is easiest to filter those out yourself from UNIX or elsewhere.

Thank you ArndW!

I can easily filter it but I still need the complete message text as one line input to my looping logic in the UNIX script.

Your SELECT output is comin into your script on stdin, right? So just filter it with "tr -d '\n' " and you've achieved your goal.

That is true ArndW but that would also remove line breaks between each output row as well which I need to keep.

Change your query to Then convert the '*' character back into a <Lf> after removing all linefeeds; use some other character if the '*' appears in your text.

There is no general solution, because there is an upper limit on the device width but there is no upper limit on the size of MSG.TEXT.

Thank You Arnd & Ray!!!
I will work on Arnd suggestion to get what I required.