DSXchange

Out of curiousity, why do you ask? What are you thinking about doing that you would need something like this? I have been working with the tool for quite some time and never once felt the need to do any such thing, hence the question.

Now, that's an entirely different question - and not one to be answered in a simple post. Search the forums for "BCI" and perhaps even "SQLExecDirect" to get some idea of what road you are looking to travel down.

For example, a recent series on the subject:

http://www.dsxchange.com/viewtopic.php?t=115619

Yes.

Hmmm... so is Aramis already spoken for?

[raises hand] Umm... I'd like to be a Musketeer.

No, not directly. But yes - if you can store the value somewhere (USERSTATUS, flat file) and then pass it to other jobs as a job parameter.

What does your data look like coming in?

Any value you want, it is simply the key which identifies the sequence. And 'left pad' the output with zeroes to get your 8 characters:


One way.

The hashed file approach is bog standard DataStage Server stuff. Replace your two ODBC lookup stages with hashed file stages (and build something to do the initial population, if needed) and you'll be fine. As noted, make sure the hashed lookup is either not cached (my personal preference) or set to...

Meaning you couldn't read the file or load the data with tabs in it? For the latter, remove them inline with EReplace or Convert:


That will remove them from the field. For the former, we'd need more specifics.

You posted this exact same question last Wednesday. Why do you feel the need to post it again?

If you have a problem with the answers posted so far, say so. In the other post.

That's not decimal but rather hexadecimal. I would imagine you should be leaving this 'message id' as a varchar as it would be a rather... large... decimal value when translated. Too large.

Welcome! Perhaps you should post this 'perfect' script.

As noted, a SysAdmin or System Administrator. The Root Wielders. The people in charge of your UNIX servers.