DSXchange

I haven't touched it for 3 years and I'm still learning new things.

All of that can be found at the link I provided.

Source from a Transformer, something you can only do in a Server job. Set up whatever column(s) you like and hard-code any values. Make sure you do two things and it will be happy: 1. Add a stage variable. You don't need to use it, it just needs to exist. 2. Add a constraint of @OUTROWNUM=1 so it on...

There is another "job number" that this could be referencing. That's an alias you can assign to a job if the job's name is long and unwieldy so you can reference the number in the dsjob command rather than the name.

Sure. Probably need VPN but they should be able to help with all that, assuming they approve. And make certain you match the client version to whatever the server is at that you need to connect to.

OK... I'll start. "Junk" values?

Regardless, you should be able to use the double convert technique to remove all of the good characters and if anything is left then it is "invalid".

No. While you can install the client and technically "run" the client tools like Designer, there's no "begin a new project" or do much of anything without a server and a project to connect to. Will your employer or client allow you to connect to their server from your personal PC?

Didn't say that. All I said was you can't use your Windows XP PC as anything other than a client.

There is no modern version that supports XP as a server install. And requirements are spelled out on the IBM site:

http://www-01.ibm.com/software/data/inf ... ments.html

If you are asking if there is a free or 'trial' version available, there isn't.

Welcome. That's a pretty wide open question and can depend quite a bit on the person. It can also depend on how much "computer" experience (programming, UNIX, scripting, etc) you've had and if you've used a different ETL tool before. I'd say in general that it doesn't take much time to &qu...

No, the comma is part of the data in the second field. Doing that would make the second record parse out as five fields instead of four, I'm afraid.

Only on one certain day of the year.

There's also the classic one about "the spirit is willing but the flesh is weak" allegedly being mistranslated to "the wine is good but the food is bad".

You'd stand a better chance of reading this in a Server job or failing that, a Server Shared Container in your PX job with that Sequential File stage in it. It is more forgiving of issues of that nature.