DSXchange

Because a SQL statement is not the same as a DML statement. Only put SQL in the user-defined area. If you need to do DML, use before/after SQL with an anonymous block stored procedure, do your drops outside a transformation job, or switch to using a stored procedure.

Some ideas: Write+Execute permissions on the directories, userid executing the job not having permission to those directories, too many jobs having dynamic hashed files open at that moment (T30FILES setting), no space on device.

You probably had an orphaned process from a previous failure. If you stop a job or it aborts, sometimes a part of a job that's talking to a database stays active. The next time the job is run, weird things happen if a thread is out there. Use "ps -ef |grep phantom" and look for parts of your job and...

Please post the complete error message.

The message is simple. The expected file is unable to be opened. Check path, name, and permissions.

Please read more about hashed files in the recent newsletter. You lack the full understanding of how they work. Here's a copy from awhile back:

http://www.dsxchange.com/viewtopic.php?t=85364

Always pass a static date value to processes because of MIDNIGHT cross-overs, never use system date calls.

Use the correct syntax:



and put some jobs into the .dsx file. I'm assuming you've just got a function.

Your question requires at least 4 hours to verbally answer and show the various pros and cons to the most common architectural solutions. Are you doing batch ETL, micro-batch, realtime, one-time data migration, billions or millions or thousands of rows of data? Do you have unlimited budget and devel...

Post your command line syntax. Did you specify the output directory?

All you've done is remove the aspect of job control. You're sacrificing the ability to manage the number of parallel tasks occurring, as well as the ability to only re-run portions of logic. You've also made it more difficult to test just one portion of the job, because you need to run all portions....

Search the forum for releasing job locks.

I think this has been answered for you already. You have high ASCII character set values in your hashed file primary key. You need to change these to other values, being aware that just removing the values make remove the uniqueness of the key. Consider using the OCONV(link.column, "MCP") function t...

here here

Try replacing the intermediate sequential file with a transformer stage. You'll get the ability to add a reject link, which could trap out the rows being rejected from the hashed file stage.