Creating individual .DSX files for my 800+ jobs

A forum for discussing DataStage<sup>®</sup> basics. If you're not sure where your question goes, start here.

Moderators: chulett, rschirm, roy

Post Reply
laiko
Premium Member
Premium Member
Posts: 35
Joined: Sun May 25, 2008 10:55 am

Creating individual .DSX files for my 800+ jobs

Post by laiko »

We would like to check in all our DS jobs to CVS. How can I create individual DSX files for all the jobs? -- well, apart from doing it one-by-one in Manager :(
Thanks in advance..
nagarjuna
Premium Member
Premium Member
Posts: 533
Joined: Fri Jun 27, 2008 9:11 pm
Location: Chicago

Post by nagarjuna »

Nag
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

That or one-by-one in a scripted loop.
-craig

"You can never have too many knives" -- Logan Nine Fingers
laiko
Premium Member
Premium Member
Posts: 35
Joined: Sun May 25, 2008 10:55 am

DSX Cutter not working for me..

Post by laiko »

nagarjuna wrote:Check this post :

viewtopic.php?t=113429&highlight=cutter
I tried to use this script to create individual .DSX files for each job inside the category which I exported. When I did the export, I only checked 'Job Designs' as Component and 'By Category' as Option. When I ran the 'perl DSX_Cutter.pl filename' where filename is my category .dsx file, it created the individual .dsx files, but filenames end in '?.dsx'. I renamed the files by removing the '?' . When I tried to import the files, I get an error 'No Objects found for import' - and nothing gets imported.

What did I do wrong????
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Hard to say... what's actually *in* the .dsx files the cutter created?
-craig

"You can never have too many knives" -- Logan Nine Fingers
laiko
Premium Member
Premium Member
Posts: 35
Joined: Sun May 25, 2008 10:55 am

Post by laiko »

It has the header (which is also in the category .dsx) + its own individual scripts. Something like:

Code: Select all

BEGIN HEADER
   CharacterSet "CP1252"
   ExportingTool "Ascential DataStage Export"
   ToolVersion "4"
   ServerName "My_Server"
   ToolInstanceID "My_Project"
   MDISVersion "1.0"
   Date "2009-05-28"
   Time "10.43.29"
   ServerVersion "7.5.1.A"
END HEADER
BEGIN DSJOB
   Identifier "My_Job"
  ... 
END DSJOB
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

So I assume the ". . ." is where you hacked out all of the job itself, yes? As a test, export this single job manually from the GUI and compare the two output files. That should help give us a clue as to what may be missing.
-craig

"You can never have too many knives" -- Logan Nine Fingers
Post Reply