DSXchange

And Sequence jobs are discussed in the General forum, being job type agnostic.

So... do we have a resolution now?

Then look at the various dsjob options as noted, for example -ljobs to get a list of jobs then loop thru them and issue a -jobinfo for each one.

I have no clue, perhaps others might. Seems to me you are rapidly sliding into Official Support Provider time, if you haven't already contacted them.

You need to build a job to do this or can you do something from the command line? I ask because you can script this using dsjob which can be simpler for people if they haven't done much work with the DSGet* API functions and BASIC.

True... in the intervening years we've figured that out but haven't gone back and tried to back-fill things. Thanks for that.

OK... I'll spell it out for you.

1. License the number of CPUs you have on your server
2. Decrease the number of CPUs on your server to your license limit
3. Live with having that warning in every job run

Then you've got a problem. You are licensed for X CPUs and have >X on the DataStage server. I'm sure you can figure out what your options are here, yes?

Check and see if your field is indeed being padded with that character, in Oracle I would use the dump() function, hopefully there is some kind of DB2 equivalent.

I would start here - "Please contact Ascential Client Support or your Ascential Account Manager". Not sure what the proper answer would be in a grid environment but I'm sure there's some way to handle this.

I'm assuming the "deadlock daemon" is still around in this version, it is something that would periodically clear things of that nature for you. Search here for the details on enabling / configuring it.

An exact search for "It is not legal to set a reducer" should answer your question.

<click>

Fixed your... rather strange quoting of yourself for you.

Perhaps the API stage is padding with something other than spaces? As noted, it cannot behave as if it were a varchar so something must be there... what is your PADCHAR?