DSXchange

What we have implemented still requires a lot of jobs and hand coding. Vincent's way is far more flexible.

We allow developers read only access in production. We do this in UNIX permissions on the project directory. It can cause problems if they try to Save As on a job or Copy then it can lock \\NEXT... record in DS_JOBS which is a big problem.

We implemented something like this in our ODS. We have business rules in a table. These have unique IDs. The table stores whether or not the rule is a DEF - default value, LK - lookup and other rule types. The rule has a state applied to each record. The state says whether or not to reject the recor...

Ray is saying it can be done but it is not documented. Therefore probably not something IBM thinks you might need to do. I think Craig's question is still valid. Why?

EtlStats is a set of jobs to pull all kinds of metadata. There is really only one job which pulls the run time stats. It is called DSJobReportDb. It has a before job process which runs: dsjob -report ProjectName JobName XML >JobName.xml This JobName.xml file gets read 3 different times. Once for row...

Most of PX jobs store table names in a property field. There is a job in EtlStats which extracts this info and loads it to a table called ETL_PROPERTY. Try that and tell us what else you need. You are going to have extract it a little at a time this way.

Sorry but the scripts posted need to go in C:\DataStage\KimD\Scripts and you need to create C:\DataStage\KimD\Backups. Without editing the scripts you are stuck with these directories. I think this is fixed now but I have not posted updates to these in a while.

Not sure which version you are using but create this directory and try again.

In order to restore these hashed files you need to understand the internals of DataStage. One job is stored in many hashed files. It is not worth the effort to restore all these hashed files to get one job back. I can easily restore any job from an export. A lot less effort. The job can also be rest...

Ray, I am not sure I would of answered this based on the topic.

I misread the question. In server the oconv/iconv are smart enough to convert these. I am saying on the first one if we validate on a DATE type 2008-06-16 we are failing. The job is failing hard when it gets really bad values. The purpose of this function should be to tell us it will convert without...

I think it is a bug. It should validate in as a DATE.

This is not a discussion. A discussion is 2 people trying to learn from each other. This is one immature person trying to promote himself at the cost of others. Others who have invested lots of their valuable time and effort to help make all of us better DataStage developers. You are not helping any...

ag_ram I have been using Universe since 1986 and I would never do any of this. Export/Import is by far the best way to recover a job. Your advice seems to be misleading on purpose. If you keep giving bad advice then we need to ban you or do something drastic. You argue with Ray, Arnd and others, our...

I do this all the time. In EtlStats there is a driver job which runs the get row counts job for every job in project. You could do the same for this job. Just write a job which loads all plants into a hashed file. Run the job in a loop after you select the plant names from the hashed file. This is c...