DSXchange

Try with that, I dont know if you will get four spaces. Thats why I advised to use char in the first place. I know for sure with char you will get four spaces. You can also use modify stage for explicit data type conversions. Otherwise you can specify x number of zeros where x is the length of your ...

dsenv contains environment variables. For more info refer to the DataStage help manuals that are shipped with the product. uvconfig file contains configuration parameters for the DataStage engine. default.apt file will point towards the configuration file for parallel jobs. This is set by APT_CONFIG...

Well when I said 'Specify it as char', I meant specify it as char and take care of the explicit conversion. On second thought, if you leave the decimal values as decimal and specify the fill character as 0 you should be fine. This way for decimal(4) if you get 123, you will actually write 0123 to th...

Specify that as char as well. A fixed width flat file should contain all character fields to honor the length.

Specify it as char instead of varchar. Specify the length's properly. Set the APT_PAD_CHARACTER to space " ".

Thats a nice piece of document Ray. Did you prepare it?

On second thought, use IsValid()

Welcome Aboard,
There is a function AlNum() in the px transformer that performs Alpha-numeric checks. You can probably use that function.

No you dont need to. Change the char's to vharchars and see if you see any difference.

I cannot remember what happened back then but if it were a compilation error then I doubt it would be anything more then that, but I will try to be more precise, than I was almost a year ago .

Reading Vincent's complete reply in your embedded post, it seems like he is warning that if the job is in STOPPED/RESTARTABLE state, it needs to be reset and then run. So I guess it needs to be reset and is infact a missing feature. Dont know about version 8.0

It must be a fixed width file with char fields. It will pad empty character with APT_STRING_PADCHAR. What do you want it to do? You dont want the empty characters? Then it wont be a fixed width file.

Thats strange. I built a job and after testing with '%' , I confirmed that it can be used. I dont have access to the manual so cannot test with other operators, but know for sure '%' works.

As a different approach. Put all your values in a line in the format it should appear in the sql clause. In the execute command stage read the contents of the file type my/fully/qualified/file.txt Pass the Execute_Command.$Output<1> or Field(Execute_Command.$Output,@FM, 1) as the derivation for the ...

Metadata delivery status huh! Well we shall tackle it when we get our hands on the product. I am sure folks like you and Kim will break through it.