DSXchange

Are they really numbers? After all, the only data type in a text file is "text". Try performing some arithmetic on them, to force them to be numbers (adding zero is the most efficient). If you get errors ("non numeric where numeric required") you will know that what you have in the CSV file are not ...

Handling referential integrity in DataStage - like in any other realm - is as simple as making sure that referential integrity is not violated. To do this in DataStage, you need to have accessible a reference lookup to the referenced column values in the referenced table when loading the referring t...

You could use mv in an after-job subroutine, or in a job (or job sequence) that controls this job. Use back quotes to capture that part of the date command's output that you require. For example (from AIX; use -f5 for Solaris, etc): mv `date +"%c%m%d_%H%M%S" | cut -d' ' -f6` If you're usin...

Can you be more specific? I am guessing that you want to tag the file name with a timestamp of some kind. There are two approaches to this problem, searching the Forum will yield detailed solutions in each case. Write to an untagged file and change its name using mv (and `date`) subsequently. Create...

You must have the same set of columns defined on the Outputs link of the ODBC stage as are delivered by the stored procedure. DataStage only deals with stored procedures that manipulate rows of data; either deliver them or accept them. In your case DataStage wants the stored procedure to deliver one...

Yes, you can have a great deal of free time by requiring their specifications to be documented. For example: Which row count? Row counts are different on different links (for example they are ideally zero on reject-handling links). What is their business rule for "timestamp"? That is, which particul...

Question your need. This information is already captured into the job's own log (which happens to be a table in the Repository). You can print, or print to file, from the Director client on those odd occasions you genuinely need to capture these data into a file. Yes, you can do it all in code, but ...

&PH& is a directory, but the ampersands in its name mean that it's tricky to get at; ampersand is a meaningful character in the shell (it means "start a background process"). To get there, you need either to quote the name ( cd '&PH&' ) or escape the ampersands ( cd \&PH\& ). All files in the &PH& d...

Sage advice. You can cat the remaining three to the first, and make the rm command conditional on success of the cat command, using ordinary shell operators, for example cat file2 file3 file4 >> file1 && rm -f file2 file3 file4 The same can be done on Windows, use type instead of cat and del instead...

TIMEDATE() function returns the current date and time in a non-standard "timestamp-like" format. The documented way to retrieve the job start is to use DSGetJobInfo with an InfoType argument of DSJ.JOBSTARTTIMESTAMP. The time component is in external format; you can retrieve it with substring or Fie...

As you know from another thread, every DataStage job is assigned a unique number by DataStage itself, the mapping being recorded in the DS_JOBS table. However, it's impractical to rely on this for your purposes, because you have no control over that number, and it's unlikely to be the same in your d...

Lots of places do this by maintaining a separate table (so as not to muck about with the Repository). Michael's approach, using the description, is about the only safe way to use the repository tables to achieve this end. He forgot to tell you that, if you're more comfortable with SQL, this is also ...

Do you have NLS (National Language Support) enabled in DataStage?
If so you can use mapping on the inputs and outputs. Internally, if NLS is enabled, DataStage uses an idiosyncratic UTF-8 encoding of Unicode.

Only a limited subset of metadata for the columns in Repository tables is published. The remainder are deliberately suppressed; Repository tables are meant only to be accessed programmatically, after all, and programs don't need column names to do this. Publicly-accessible columns in DS_JOBS are: NA...

The Capturexxx files are caused by the EXECUTE statement (which is invoked within such calls as DSExecute, ExecTCL, etc.). Other internal processes, such as sorting, can generate temporary files. Part of the file name is the pid of the process that generated it. You need to track back to the records...