DSXchange

I prefer to look at the price as a matter of time instead of as a dollar (or yen) amount. Nobody here is using DataStage as a hobby, everyone interested in DataStage is going to be using it as part of compensated work. Take your salary and compute your hourly wage. Then compute how many hours of wor...

Or turn off runtime column propagation for the modify stage and only KEEP the one column you are interested in.

Ray - that is what I first wrote, but then realized that the routines are the same ONLY for before/after job subroutines, and that wasn't what the poster was asking.

I am not quite sure of what you are doing, so I cannot answer directly. The lookup stage needs to match the source and target columns in order to work. In you case, what is the data type and format of the main data stream and what is the data type and format for the reference. Is the reference the X...

Try converting all of your COMP fields to correctly sized PIC(x) columns and read the data, see if the contents of COMPANY and DIVISION remain correct - in that case you have correct length. Then change one COMP-3 at a time and see if the conversions work.

Odd - co you have one import of the copybook into your DataStage metadata and are inserting that definition into both jobs?

[quote="arun_kumar]...But writing subroutine in server jobs is completely diffr from parallel...[/quote]
It is different, Server jobs require DS/Basic knowledge, PX jobs require C or C++ knowledge.

When you define a Decimal they do. You can check the generated c++ after a compile and see where the precision and scale are used when defining the stage variables.

Compiling a DataStage job generates several types of objects, only some of which can be seen at an OS level. Some of the generated code are OSH scripts (i.e. a specialized scripting language) and transform stages are actually c++ programs and object code.

There is no ready-made BATch file to do this, the posters have just supplied the raw command that will clean up a dataset and you will have to write an appropriate file. If you have orphaned datasets, i.e. where someone has deleted the descriptor file without using orchadmin rm , you can look at thi...

One job can only run once at a time unless you specify that it is multi-instance. There are considerations you need to cater for when writing a multi-instance job, i.e. such as making sure that you don't write to the same sequential file as the other instances of the job.

The PIC X column, ARS-NAME, shouldn't cause problems. If it does, it probably means that your record length is off and binary information is being parsed as part of that string, most likely your definition is shorter than the real data and the contents of the subsequent COMP-3 field are coming into ...

Any time you get a 'dropping component' warning it means that DS thinks it has two columns of the same name going downstream; and in most cases this is because you have ntime column propagation turned on. You should fix this in your code to get rid of the warning. Sequential files can only be proces...

DataStage Server and PX allocate resources in different ways. You posted with a product of Server so we'll stick with that side of things. The configuration of the Server environment is controlled principally through the settings in the UVCONFIG file and in most cases the default settings are also t...

There is no builtin SMS send utility in DataStage, but most service providers have utlities that redirect email to SMS. Since you can call programs from DataStage and all mail utilities that I know of have some sort of command line interface you can solve your problem that way. DataStage even comes ...