DSXchange

mike - I'm a bit chagrined by your response since the FAQ that I wrote explains exactly how to locate such orphaned files.

Type 30 is a dynamic file, the hashed file will be created in the project directory(you will get a file "D_MyFile", a subdirectory called "MyFile" with 2 visible files and a hidden file). "see the file"? That would be from the TCL command line using "LIST" or ...

Of course that will give incorrect output. In order to do ANY date work, DataStage (and you) need to know what actual date is represented by "09134" -> is it Febrary 13th, 1242 or December 1st, 2005 or some other date? Once you know that date, then you can use the DateFromDaysSince function.

karrisuresh - the problem is that if you delete the descriptor file by mistake then you have no way of knowing which of the files in the dataset directory are "orphaned" and will never be used again; therefore your suggestion, while being the correct way to do things in a perfect world, wi...

The working directory of the DataStage job and thus for any shells called from it is the DataStage project directory - so you should put an absolute path in for any file operations to make sure that they are correctly addressed at runtime.

There is, unfortunately, no single definition or standard for "Julian Date". But DataStage has a function DateFromDaysSince() with which you can take the base date from your Julian and add the number of days to get a DATE value, which you can then format to your specifications. If your jul...

the transformer in PX has the same set of string functions as Server. But if you have fixed width columns with no separators it would make more sense to declare the columns appropriately in the sequential file stage and save reconverting them in a transform stage.

The first entries in your job log will contain, among other things, the DataStage job's ENVironment settings. The odds are in favor of finding that the path to that directory in not set. It might be set for your login, but DataStage uses the settings as defined in the "dsenv" file.

The short answer is "no". The Transform stage is compiled from the generated cpp code and the parameter runtime value is just inserted, so any arithmetic or logical operator in the parameter is treated as a string. i.e. in your case the statement would be IF "5<4" THEN 1 ELSE 0[c...

Analysis for this would be:

1. use UNIX "find" to locate the directory where "dsstpora.so" is located.
2. Make sure that this directory is in your PATH or LIBPATH environment variable (depends upon whic flavor of UNIX you are running)

Can you make your Oracle stage do upserts as well and see if, for some reason, the update option is being taken?

mhester - unfortunately, the ".ds" descriptor files often get deleted using OS commands, leaving orphaned (large) data files, so one needs to find all descriptor files, and any data files that don't link to a descriptor are orphans and can get deleted. I posted This FAQ on Magic/Orphans wh...

I would look at how you are reading your data - each database has different syntax for ensuring that you select without taking locks. In addition, you need to ensure that no 2 nodes can update the same records - the easiest solution here is to partition on the database key. Another easy, but ineffic...

Is your question whether one can write a DataStage job to read a CFF, modify it, and write a CFF file with the new format? In that case the answer is "yes".

a "CHAR(2)" defined column cannot have just one space.