DSXchange

You could write your own INLIST type function, such as one posted here: m to simplify some of what you're doing. Ray's suggestion to use a stage variable to hold the 3 char substring you're using over and over is another good idea. You may consider writing a BETWEEN type function so that you can sim...

Try "man grep" on your version of Unix. The "-v" option should be available for returning non-matching rows.

DS is setup for NLS. From Administrator General tab, I choose hit NLS button. I go to Client/Server map in use pull down and choose UTF8. Error message comes up: Map 'UTF8' is unsuitable for client/server use - Does not map the UniVerse mark character IM to a single byte. I hit okay, message comes u...

madhonrougeuri wrote:Hi,
Could any body tell me in what case is before/after sql used in OCI stage..any examples?

Thanks.

For Oracle, you could find uses such as:


Or

Or

Parameters are fed as:



You aren't specifying which parameter gets what value.

ray.wurlod wrote:The expression (If Club = 'c' THEN COUNTRY_CDE = '2' else '0') can only return "2" or "0".

Ray's statement is wrong. He should not have the "COUNTRY_CDE = '2'", just " the '2' portion. Craig has been trying to point this out.

See this post: m You can use DS_AUDIT as a means of identifying what objects have changed in a project, but for internally on the object, you must do a .dsx comparison. However, this may not work because of the internal numbering scheme on object designs. The internal numbers change as you do things...

You must return your answer in a variable called 'Ans'.

Execute a Unix concatenate statement. If you carefully used a naming convention where there is a common portion of the filename, then simply use a cat statement with a wildcard. Example: All of your jobs wrote out an error file for "FRED" table under the name "FRED_yourjobname.dat". You can then exe...

To add onto Arnds points, you also have an UNRESTARTABLE design, which you should always try to avoid. Job A --> creates sequential file and writes 1000 rows. Job B --> appends to file 1000 rows = 2000 rows total Job C --> appends to file 1000 rows = 3000 rows total Job D --> appends to file 500 row...

Use multiple job instances and divide the source data into N groups. Use N instances to process the data in 1/N less time, where ideally N is the number of cpus available. Remove all database reference lookups, using hash files. If a single instance fails, re-run just that instance.

Something internally is messed up. Export and import the job.

You have a incorrect variable or column name being used in an expression, problably as part of a conditional (IF..THEN..ELSE) that occasionally will take the opposite path. When doing so, it encounters the coding error. Search this forum for looking at RB_BPxxx files to read the physical job code an...

Please search the forum, we've been having lively discussions about it lately.