DSXchange

Not going to hurt anything for you to try this, there's not all that much too it other than a need to bounce DataStage. Give it a shot.

FWIW, my T30FILE value is 1000 on our dev/test server.

Without knowing how many jobs are 'all' jobs and how many hashed files are involved here, I'd suggest doubling both those numbers. You do know you have to "regen" after any uvconfig change, yes? Others will need to address the "risk" question, for those I'd think it's only a matt...

You started another post to continue your same issue? And this time in a completely inappropriate forum? Come on.

And you really need to understand the difference between a full (or 'fully qualified' or 'absolute') path and a relative one and what a relative path is relative to.

There is no other way. 'Large Object' Field types like BLOB or TEXT fields are simply not supported. Move / process them with whatever native tools your database provides.

That's the problem - it doesn't. Or to put it more properly, there are many times where data is rejected that does not make it down a reject link. Everything looks happy happy until you take a closer look at the logs. Makes much sense, it does not.

rdgstar wrote:This happens when all jobs in the project are running. When a job run stand alone we don't get the error.

One option would be to not run all of the jobs in the project at the same time. Stagger them out a wee bit.

I'd also bump up the two uvconfig file entries you posted.

There's no "looping" inside a job, there is however "aggregation" which this seems like it might be.

Job Control code != JCL, btw.

As you are finding, that's just The Way It Works. Certain errors happen silently and are only visible upon close examination of the logs. We've found you really need a routine to examine the logs after job and abort the job (or issue some kind of alert) when those conditions are found.

You'd need to do a much better job of what "I can't view the file" means for people to help. What happens? What list is generated? Details, man, details!

Why are you trying to 'set' a job parameter that's actually an environment variable? There's no need to do that as it will automatically pick it up from the... well... environment.

And yes, you'd either need two triggers and a Sequencer or a custom trigger to allow a downstream job to fire if the previous job finished OK or with Warnings.

The Sequence job itself will generally finish fine, regardless of how many warnings the jobs it runs have. Options like the 'Automatically handle activities that fail' can change that behaviour, or course, of the use of a Terminator stage, which cause the actual Sequence job generate warnings or eve...

Hopefully in your travels through Searchville here you saw this post of mine with the same issue. I wasn't looking for 'quickest' anything but rather the best solution which involved properly partitioning your lookup data to minimize space utilization, allowing it to 'map' things just fine. On the i...