DSXchange

Hi XiangMing,

don't start at the wrong side. If you define your fields correct you will not get any warning. Any warning, even if the result is okay tells you, that you have coded something wrong.

Wolfgang Huerter
=====================
Cologne, Germany

Hi Dick, reading Excel-files is in most ETL-environments a request. Most project I have seen do this via an export into a *.csv-file (Info for all non-anglo people here: If you do an export via a VBA-automation the anglo-type of *.csv is taken, that is comma as field seperator and point as decimal s...

It is right, any tool trying to export DataStage components gets an error when this element is looked by a user. There are ways to blow this users out, by for example restarting DataStage. But best way is to get dicipline into the designer-community. Those who have forgotten to log off have do clean...

You can write a job which reads your file and starts your next job with the parameters read in the file.

Wolfgang Huerter
=====================
Cologne, Germany

Hi Luca, best way to solve is to be 100 % correct. If the database accepts the difference even a char on the one side and a numeric on the other work. Some stage are strict. With ODBC you get for any difference even for char(4) vs. char(8) an error, some other stages accept difference without gettin...

Hi Nagesh,

the Stage for to connect in a DB-way to Universe-files (=Hash-files) is the UV-Stage, there you can do what you want to do.

Wolfgang

After having made the shared container you can undo the process on both jobs and by this you are able to copy Jobs or parts of jobs without having any shared containers left back. (unless you want to keep them)

Wolfgang

Hi BigPoppa, To get ODBC right is not easy. There are 3 place, where you have to look (and mybe change) (1) The .odbc.ini-file (2) The uvodbc.config (3) The dsenv There are also checkprogramms on the server to check if ODBC is done okay. Read the manual for this 3 places and you will succeed. Wolfgang

Version Control is coming relativly new together with DataStage, a bit shorter it could be bought for an add-on price from a third-party. Versioning should be considered in the beginning of a project, but mostly you think at the end. Most projects are already old, so at that time your choice was VSS...

Yes, Write a Job1 where you select the Table with the timestamps, than start your loadjob and give him the timestamp as parameter. In the where part of the reading select (suppose the Name of the Parameter is TimeAfter) you write Selectdate>#TimeAfter#. That is it. If this doesn't work, maybe that t...

hi Michael,

as an author of a post you are able to re-edit your post and make any changes you like, even a complete delete of your own post is possible.

Wolfgang

Hi Sanjay,

it seems to be a problem with access right. Go into the project directories. In each are file called:

.developer.adm
.operator.adm

Look that all the groups of the users are in these lists.

Wolfgang

We work since some years with PVCS. At that time no Version Control was yet integratet in DataStage at that time. For to control DataStage Elements from PVCS (for a checkin and checkout) we have used Export. Any DataStage-Ellement (Job, Routine, Transform ....) can be imported and exported into *.ds...

Hi Dick, You can access any Hashfile in any project you want if the file is in your reach. (Same server, mounted via NTFS or remote Universe) Every time you use one file in more than one job you should know what you are doing, how the writing or deleting of the Hashfile of Job A will influence Job B...

The control-file has to be written in any case if via plugin or via DS-Job or DS-BASIC-code, so you won't win anything via the plugin.

Wolfgang