DSXchange

By default the limit on jobname.invocationID is 255 characters.

This can be made larger, but I've never found a need to.

Who ya gonna call?

Clearly you have at least BG Author role (you can save new categories). The next thing you need to do is to look at the WAS logs (SystemOut and SystemErr) to determine the cause of the failure. C:\IBM\WebSphere\AppServer\profiles\InfoSphere\logs\server1 is the default location on Windows for these l...

Not really though, if you have DataStage, you could use that. Both products share the same metadata repository.

There are some consoles coming along to aid with managing these rules.

Can't tell you when, but they're in development now.

No. I don't believe so. The problem is likely to be that you have logged in to the Web Console as a user who is not a Suite Administrator.

You do have to have some kind of Engine credential, and it's most usually mapped through the interface you mentioned.

You will get zillions of errors, and it may or may not work. IBM will tell you it won't work, and that's true in many cases. Only if your 8.7 components are fully 8.1 compatible (no 8.5 or 8.7 functionality) will this have any chance at all of succeeding.

Of course it's possible, but you still need to incorporate all the logic to determine which job it is you need to run.

1. Yes (in a Routine activity) but why would you when you have the Job activity. It's going to be just as complex by this route as using Job activities.

2. Yes.

In version 8.7 they're available in the Administration tab of the Business Glossary browser itself.

The following list summarizes the Boolean expressions that are supported. In the list, BOOLEAN denotes any Boolean expression. - true - false - six comparison operators: =, <>, <, >, <=, >= - is null - is not null - like 'abc' (the second operand must be a regular expression) - between (for example...

Welcome aboard. I would guess (without testing) that the tie with the record with the highest match weight would survive in this case.

Were I the support analyst for this PMR I'd ask for the complete error message so that I could determine which stage was actually throwing the error. For example it might be a Sequential File stage somewhere else in the job design. It's really important to extract all possible information from error...

What have you tried? What did you achieve?

Or do you want us to solve all your problems for you? That's called "consulting" and comes at a fee.

Once you've run VSG over your Unidata account it should be able to be accessed via the UniODBC driver. Therefore it will be necessary to install that driver on your DataStage Engine tier. Do this from the U2 clients media (usually CD or DVD). Note that the UniData stages in DataStage do not use an O...