DSXchange

I forgot, all stages are where OLETYPE LIKE '%Stage'. This may not be perfect but it is close.

You can get this from DS_JOBOBJECTS using SQL. The NAME field is either a stage name or a link name. You need to join back to DS_JOBS using OBJIDNO = JOBNO. OLETYPE is the stage type except on PX jobs, they all are custom stages with the PX type in field 8. Do a search this has been posted.

Just kidding, Ray.

To qoute Craig, "hack cough hack".

It takes a lot of code to translate a file into parmeter values. Trust me. It is not that easy.

I would count rows and bytes from both servers to validate.

Sounds like a job interview question to me.

Thanks Craig. I had fun hanging out with you and the guys.

We have so many versions of this script now. I need to post all of these. We can export the jobs from one project and import into a second. This is our migrate script. It compiles with dscc.exe afterwards. I may post it soon.

The read only items is not a problem. These are items supplied with DataStage. It is easier to export all and cut the full export into one per job. There is a Perl script to do that. I have 2 more ways to do this. We create a file with a list of jobs we want to export called JobList.txt. We just loo...

Should get you close.

I give a lot of code and jobs away now. Dennis wants to hold back on some of this as an incentive to become a member. Depends on the demand. We may give away all my tools if you become a member. Need to make this site at least break even.

It is a little program written by me in VB. They may post source code for something like this in a members only area. If that would be something you might want then ask Dennis the Editor.

Do a search for Dwn_ExecTCL.exe.

Preston took one of these and cut out the dependent objects so now our migration script can run unattended. Very cool. We do not need to click on No to not overwrite the shared containers.