DSXchange

Interesting... what few times I've done an XML export I've never changed it from the default of 'Output internal (stored) values'. Perhaps some sort of issue with the 'localization' it does 'where appropriate' according to the help.

Anything not directly supported can be accessed via scripts.

Biggest question to me is - why do the export in XML? Unless you are doing something 'special' with the exported file, stick with the dsx format. Saves you time because, as you've seen, it first needs to convert the xml file to a dsx file before it can import it. Why add all that overhead to your pr...

Agree with the 'should'... and I'll let you know.

I was gonna suggest exactly that. Maybe bumper stickers and t-shirts:

ETLStats: Take. Adapt. Shine.

:D

I have a job that looks something up and stores that value in its User Status area for others to pluck. Based on usage, I may need to make it multi-instance so multiple 'systems' could call it without overwriting current values for other 'systems', controlled by the invocation id. Was just wondering...

samit_9999 wrote:I just receive a flat file which has data in the above format...so i need to carry the above operations in datastage.

No, not really. What's stopping you from loading it into a work table in your database of choice and working it over with a SQL stick?

Can you say 'Shites' here? Hmm... guess so. I'll have to check it out.

Juls is planning on deleting the problem project and recreating it with the same name. In that case, it sounds like they will be fine.

Read the linked discussion again, especially the replies from Arnd and Ultramundane. Read the manual or check the command-line help for the 'dsjob' command and the options it has like 'logsum'. Search the forums for same. There are equivalent DS routines to farm job logs as well if you'd rather do i...

They should still be fine, I would think. Don't know with 100% certainty as I'm not running a Windows server, but...

No, they are stored in whatever mechanism is doing the scheduling - cron, at, Control-M, etc. DataStage has no scheduler built in, only an interface to the external schedulers of choice: cron/at on UNIX and at in Windows. So, depending on your scheduler and O/S it would just be a matter of educating...

I don't think you need to install the Version 1 pack. Check and see if you have the XMLPACK_20_Designer.pdf manual in your Docs directory. It will educate you on techniques for using the XML stages to read and write XML, plus has some 'advanced' topics as well.

All your schedules are stored using ControlM scheduling utitlity. And you know this how? UNIX 'schedules' - assuming standard Director scheduling - are stored in the crontab of the scheduling user for recurring jobs. However, seeing as how the OP is on Windows, that doesn't really help all that much.

Eats, Shoots and Leaves.