DSXchange

I think that's for some other aspect of the site. This never prompts for nor mentions a password, just slams the door in my face with this message: Premium Members have full access to tips and tricks, white papers and on-demand videos. Sorry! Only Charter and Premium Members have access to the conte...

Probably the record but yes, sounds like some kind of a locking issue. Have your DBA check.

Not aware of any video on the subject but one of the best documents for XML in DataStage is here. There's also good information on all things DataStage (including XML) in Ernie Ostic's blog.

Hopefully one of the 'account issues' that gets sorted out is the ability to get to the Learning Center as a Premium user. In spite of the fact that I am, it doesn't seem to think so and won't open the door.

"Possible range limitation" simply means that your source data may not fit in the target field. Specifically in your case the double into the decimal. If you have no concerns that will ever been an issue, I could see someone demoting this to informational.

Sreenivasulu wrote:What does %(aa,w) stand for ?

Check the post the advice came from.

Details, please.

I've never seen a CLEAR.FILE hang. Have you tried exporting the job to a .dsx and then immediately importing it back? That will delete / recreate everything and assign it a new number.

Is there anywhere that Ray has not spread the word? I think not.

You would have to have 'zip' installed on your DataStage server to do this, do you? Or compress or gzip as alternatives. As to the how, it's no different from doing it directly from the command line. If you are unsure of the syntax, try 'man xxxx' to get the man pages (if they are installed on your ...

Different issue, and I would question the fact that the job truly 'finished' if there are still processes associated with it.

Only if you want a corrupted job.

Only indirectly... perhaps by dropping a semaphore file as part of your 'after job' that the other job polls for to know it's ok to start.

Hashed files don't reject records in the way that you mean, nor does a hashed reference lookup support such a concept. All you can do is check to see if the lookup succeeded or not, typically via the NOTFOUND link variable. If what you are after are the records in the hashed file that are not in you...

Pass it as a parameter into the routine or do something similar to what was posted but attach to DSJ.ME and use DSGetParamInfo() instead. And always remember to detach from anything you attach to.