DSXchange

There have been some questions here regarding checkpointed Sequence jobs with Loop stages and when happens when it aborts deep inside the loop. I had the opportunity to witness this and thought I'd pass along my experience. Complex Sequence job with stages both before and after the Loop start/end st...

That's not 'hardcoded' but fine, I understand what you mean. I stand by my diagnosis - reschedule the job, correct the parameter values stored there and it will be fine the next time it runs.

Search the forum for your warning message 'PRINTER memory segment removed', the issue has been discussed here quite a number of times.

You don't get the error 'in' the transformer stage. The transformer is the active stage, so that's why it reports the error. View Data just does a select based on the metadata, so the fact that that works doesn't mean much as it doesn't use your sql to do it. How many columns do you have defined in ...

Welcome. :D Normally, I would say that the Batch job was scheduled with invalid values for the connection parameters. That would explain why it fails when cron runs it and then works fine during a manual run. Whenever parameter values in a scheduled job need to change, you can't just change the valu...

You can echo that value of any environment variable that is currently set. Your code, minimal as it is, works fine. Your conclusions must be based on testing the routine in the Manager, which is fine as long as you understand what you are seeing. In the Manager, the only environment variables avail...

Lemon squeezie.

Me like edification.

Where are you doing this 'use an Oracle Sequence' in your job design? Are you still planning on doing this once and then incrementing it by 1 in your job?

Then either switch to the DRS stage, which does have that option for ODBC, or use user-defined sql.

Read the file and send the keys to your database stage of choice using the 'Delete existing rows' update action. Easy Peasy.

I'm really not sure how one would check that. I'd suggest you open up a Support case with IBM for this, if you haven't already done so.

I really don't understand the need some people have to quote something every flipping time. Especially something with absolutely no bearing on their reply. </irked>

So, they fail to start at all? Is anything at all in the job's log that indicates it may have tried to start? I ask because once upon a time, I saw something where the job did try to start but couldn't. The Status view in the log would not change from the last successful run, but there would be a si...

George, you really don't need to keep putting everything into both threads. Let's play here since your dsenv file is actually posted in this one. As Ray has already noted, and as should be pretty obvious from the error message, one of your file's lines is horked up. This one, in particular: SHLIB_PA...