DSXchange

Make the code write incoming values into a file so you can cross-check the failed values.

Test the code as a stand-alone before calling from datastage.

After job script - something like

Your call_terminating_nbr in 6 needs strcmp.

Please enclose the code in 'code' tag so others can see better.

Also you may reduce the burden by removing all codes after 6 and check whether 1-6 works fine.

Your call_terminating_nbr in 6 needs strcmp.

Please enclose the code in 'code' tag so others can see better.

Also you may reduce the burden by removing all codes after 6 and check whether 1-6 works fine.

Mainframe activity by DataStage is done by generating cobol and jcl codes.

Can you please clarify whether you are asked to write the code or are you trying to use existing PX to assist or are you planning to buy new piece of DataStage which will help you with MainFrame?

Pic X(2) and Pic S9(7)v99 must be straight-forward.

For Comp-3, ArndW provided a routine.

In PX, you can use CFF as output.

Is the source from COBOL structures?

Maybe it is declared as imperative signed - i.e. S.

Try 111b. Does it return -2 ? Normally it starts from p. i.e. 000p = -1.

From the look it appears to be using as Comp-9.

Maybe you can load all records into a temporary table with a serial number and constraint the load into your target table. But why do anybody have such a requirement !!?? Maybe they want to split their daily workload of checking the data !!?? What is the expected action if the following day's record...

I will forcefully write the 'No records' line first in the file even before the job starts.

Then in the job, I will write a link with @INROWNUM = 1 (or something similar) to just overwrite with same key as 'No records'.

I will forcefully write the 'No records' line first in the file even before the job starts.

Then in the job, I will write a link with @INROWNUM = 1 (or something similar) to just overwrite with same key as 'No records'.

Can you split the rows into multiple groups - something like if tableCustomer returns any rows then follow tableCustomerDetails else follow tableInternalCustomer etc. If you can split by either logic or subject area, you can break the SQL into multiple jobs with simpler logic. This way it will also ...

Server join are from static files.

You can do lookup, but you can join in database and use DataStage for other transformation activities.

Or the hash directory parameter not passed any value.

Balu,

DataStage runs pipeline parallelism mode. So the 29 minutes of Oracle extration will have impact due to stages further down the line.

Did you try applying @FALSE in the transformer stage?

If that shows any improvement, we can work on other stages to carry it till the end.