Search results for query: *

Does the LIKE statement work with % and . ?

It turns out I was missing the comma to separaate SELECT statements. Your syntax is perfect.

I want to cast the output of a case statement, but I havne't been able to get the syntax correct. cast(case when abckey like 'star%' then abckey else '' end as char(5)) as as STATUS 3706: Syntax error: expected something between '(' and the 'case' keyword.

This construct worked: '%'||trim(:dbname1)||'%' the like % % with a space in the parameter entry isn't very selective. :)

I'm having trouble getting the syntax for a like statemetn to use paremeters in a macro. I can't get the paremeters to work. Can anyone se what I'm missing? replace macro MACRO_DB.CollStatsPT_M (DBname Char (50), indicator Char (12)) as ( SELECT databasename, tablename 'FROM DBC.Tables...

I check the "use Column Names" option in my ODBC driver setup. WinDDI indeed uses the column names. Queryman uses the column titles. Can I make Queryman use column names? Thanks.

I've only succeeded by using the ROUTE MESSAGE TO FILE <filename> at the top of the script.

How can I capture the session messages?

mload < filename OR mload < &quot;filename&quot; definitely starts Multilaod but the scriptfile never executes and the mload box just sits there. Hmm.

Can anyone tell me how to invoke Mload from the <Start> <Run> command line in Windows? Thanks in advance.

How do I get BTEQ messages wirtten to a Windows files without using an .export file? Or is that required?

I have not been able to get the message directed to a Windows file. I've tried the > and >> but that hasn't changed anything. There's nothing more required than to add the file name to the BTEQ command line?

Did you ever figure this out?

My Bteq invocation is in my bat file. Do I have to break it up to route to an <outfile>? I'm using Windows Bteq.

That works. Thanks. How can I save the output from a batch bteq?

How do I invoke BTEQ to execute a batch job/script in Windows? When I tried to invoke BTEQ in a script, I got an error. If I cut and past my script into an open BTEQWIN session, it works perfectly.

CSUM on a column(count-iem AS 1) in the select clause and if the CSUM is in a view things come back in a different order than if it isn't in the view. With the CSUM in the view, I can't generate the same CSUM numbers. How does CSUM relate to the order in which rows are returned?

Stored procedures can contain any SQL DML or DDL statement (including stored procedure calls) but that the only type of SQL statement that can call a stored procedure is the &quot;CALL&quot; statement which can't be combined with any other type of SQL statement. Is this right?