DSXchange

Nope, not hex, not packed. Looked like Zoned Decimal for a second, but it's not that either. Ask your mainframe folks what that 'D' is supposed to represent.

The FMT command can handle the zero padding and the descaling of the number to remove the decimal point.

There's no problem creating a static hashed file as you are doing... something else must be going wrong. Perhaps try adding an explicit transformer stage between the two and see if that makes a difference - it shouldn't, but you never know and then at least that consideration will be off the table.

Technically there's only one delimiter - the comma.

Why do "ls -m" and complicate things? Why not use "ls -1" instead?

Unless this is another one of those things that are different in PX, stage variables are not declared as any particular datatype or length.

What does it tell you when you click the 'More' button?

anupam wrote:I want to start the Sequence Number from 1 in each case.

Then it doesn't necessarily sound like you even need a Sequence number generator. Are you saying that you need to start them at 1 each time the job is run? If that's the case you could just use @INROWNUM.

There seems to be an echo in here.

More to it than that, I'm afraid.

For one user written routine to call another user written routine, it must be declared within the calling routine. Search the forum for the usage of DEFFUN and the DSU prefix for examples.

You'll find one such example here.

Rich, curious how that's different from what they already tried and asserted "is not at all working"? They seem highly equivalent to me.

But when we initialize a project to version i could see jobs named with new version as job.name^1_1.... hence it makes the usage odd. i.e, when we try to export a catogory, the new version also add it to the dsx... Version Control has simply appends a version number to the job as it is "Initialized...

Ok... clear as mud now. These "five fields" are in your input link or the reference hashed file? What does this hashed file look like, by the way - what data fields, key fields, data types, etc - and how was it populated? Give us a better picture of your job and how you are handling the key expressi...

Yes, in essence, they shed their mortal coil when they hit the bottom of the transformer and have not been selected for advancement down any of the links. Poof.

You can't "compare" a null value to anything. By definition null is the unknown value and all you can do is ask if it is null or not null. A compare will always take the "false" path, not throw an error. And you do recognize the fact that '' (or quote-quote) is an empty string and not at all the sam...

White space is not supposed to matter in SQL. However, as you are finding, it does ... or more properly - it can! I've seen people add all kinds of blank lines and carriage returns to either generated or user defined sql so it is "easier to read". Bah. If I'm really worried about it, I'll copied the...

This doesn't really make any sense. What are you trying to accomplish?

This kind of thing would typically be done in a custom routine and then (possibly) call the routine in the derivation of a stage variable.