DSXchange

Custom triggers to make the decision about which validation job to run, separate Job activities for each of those jobs.

Your default format string for timestamp expects YMD order but you are providing MDY order. That's basically what you're doing wrong.

What about opening ports 9080 and 2810 ?

I intend not to load the job, when the same can be achieved by other lightweight stages like column generator and/or modify stages. You are relying on out-of-date knowledge. These days (since about version 8.7) the Transformer stage is no less efficient than most other stages, sometimes it's more e...

You can try forking background dsjob processes. For example

You can look at the job log in Designer. Press Ctrl-L to enable/disable, or use the View menu to accomplish the same.

Please verify that each column to be mentioned in the WHERE clause is identified in the metadata as Key

Also check that the passwords for the WAS admin user and the IIS admin user have expired/changed without the appropriate script (AppServerAdmin) having been run.

There's no other information in the job logs, either of the sequence itself or of JA1 or JA2?

Please note: it's SEQUENCE, not Sequencer. A Sequencer is something that you can use in a Sequence.

Anyone? :roll: Learn patience! This is an all-volunteer site where people post as and when they can. Yesterday, for example, I had a breakfast meeting with management, a busy day at work, and a training session at IBM after work. Not much time for DSXchange. The issue many times is that the job mon...

I'm not aware of any either, other than manually calculating row sizes based on information in Chapter 2 of Parallel Job Developer's Guide about storage sizes of data types. And anything you put in to calculate the same would degrade the job's performance. But, of course, any data moved around in pa...

Are you permitted to use a Modify stage?

If yes use a column generator to generate "Y" for all rows then use the Modify stage to convert the NULL from left outer join into "N". And/or use a fork/join to split the streams based on the result of the join (or lookup).

Maybe Sybase suppresses it. You need some way to look at the data in raw format. Try getting a CSV dump of the record from Sybase.

Probably there are non leading zeroes because the actual leading character is a space (" ") occupying the sign position.

I thought Gibberish was the language they speak in Gibraltar.