DSXchange

In other words, it's a Work Around.

Are you saying that you are still doubtful? If you're good now, please mark the thread as Resolved.

More to it than that my friend. 'ASC' and 'asc' mean two slightly different things, for instance. It's all in the help.

Did you... read the help in the stage? Put your cursor in the sort field then click on Property Help - all will be revealed.

Please state your requirements in English, not Informatican.

You are configuring this for ODBC or OCI? The first two files you mentioned are for ODBC while the third is needed for OCI. LIBPATH = SHLIB_PATH on some operating systems, you set whichever is appropriate for yours. You also need to make sure ORACLE_HOME is set in the dsenv file as well, then stop a...

Doesn't really answer the question, but... ok. Whatever.

Why not just 'analyse BASIC' by studying the supplied Routines? There are a plethora, documentation is decent and all you have to do is double-click on one to reveal the BASIC source code.

If you were on a UNIX server, I'd suggest writing to '/dev/null'. From what I recall, there is an equivalent on Windows but not sure what it is off the top of my head. Anyone?

Ah... Chuck snuck in right before me.

Yes, but it will just be created for you. If it is too much of a dummy it will cause the job to abort. It would help if you explained why it is 'irrelevant' in this case, I would think, so the suggestions can be more... targeted.

The 'RTI package' no longer exists, it is now known as the 'SOA Edition'. RTI stood for Real Time Interface and SOA allows jobs to be deployed as web services and run in 'real time'. There's more to it than that, but there's the Executive Summary.

Balakrishnan wrote:var1 = Trim(UnixOutput,'@FM','')

The quotes are your problem, they turn the Field Mark system variable into just another string.


Will work a little more better.

Not sure if this is significant or not, but I do have the ECASE 62595 patch installed which helps avoid a 'stack overflow' problem with long running loops. FYI.

I'm just curious why you are taking this path rather than creating Routines in the Manager or coding in the Job Control tab of a Server job?

You can fetch all messages from the current run of a certain type - warning, fatal, whatever you like.

After the job has run, you would fetch this information from the job's log. Techniques have been discussed here a great many times, search for the wealth of good information you'll find here. Yes, you could use another job that leverages the various 'DSGet' functions that access log information, or ...