DSXchange

Jeez, what a bunch of anal little monkeys. :lol: It's not about deleting just the ".ds" files, but if you actually read the starting post rather than just chime in midstream you'll see it's about deleting all datasets (which are stored in one location) so they can be recreated fresh in a n...

Good to know, thanks. So, back to the original poster's dilemma... you're saying that it must be there somewhere and they just must not be looking in the right place, yes?

Your monitoring would need to handle that, be it a wrapper script or an Enterprise Scheduler. And that 'message' can be as simple as an email to your mobile telephone number.

There's no guide or manual for this. Your jobs themselves should migrate over with very few if any issues. As noted, what you need to identify are any areas where you are relying on or leveraging the underlying operating system since that will be changing. So before or after job ExecDOS activities w...

The "easiest" solution would be to load all tables in one job using a single target stage with multiple input links and a transaction size of zero, then the rollback would be automagic across all if there is any failure. With separate jobs, since anything in a job previous to the failure w...

I can't check right now, but seem to recall something about a right-click option that either allowed you to save it in another format or copy it to the clipboard... and then print the result.

From a Windows server it would be ExecDOS. And code in 'Job Control' is not visible to anything inside your job proper.

Looks like a line break problem, meaning something is two+ lines that should be one long one. Open it in vi, type ":set nu" (without the quotes) to turn on line numbers and check that.

You'd have to use "rm -r" to recursively delete the folder and everything in it but yes, you're right.

Of course you can.

And please start a new topic for your new, completely unrelated question.

Interesting... what about all of the other 'optional' plug-ins, are they no longer optional and you get all of them installed whether you have a need them or not? Probably the safest route for them to have taken.

And just to address the "only if I use transformer" comment - are people not aware that's why you need a C++ compiler installed for DataStage? Normal job "compilation" for any of the other PX stages is actually a pretty straight-forward script generation rather than a 'true' comp...

In other words, the officially supported compiler for that platform I assume.

Interesting... never really thought about the possibility that moving the actual writing out to another stage would overcome this issue but it makes sense. I was always a little leary of that, afraid the Sequential File stage (as an example) could add some... artifacts... to the resulting file. :? N...

I have no idea how / if this works in 8.x but for 7.x you simply rerun the installation script and when it finds the current version already installed it defaults to 'Maintenance Mode'. There you've got four or five choices from what I recall, one of which is (in essence) a way to just add/remove th...