DSXchange

Thanks Ernie!!

I was able to parametrize the complete string in the Port Address. I was missing the # while setting the parameter.

Thanks for all the help.

Thanks Ernie!! I was able to use the parameter for the Port Address as suggested in your example .

For some reason I get an error when I try making the whole string as a parameter.

Thanks Ernie!

I was able to parametrize the WSDL.

But I was unable to parametrize the Port Address (on the Advanced Tab).

eostic wrote:...it's been awhile, but I recall in testing that I was not able to parameterize anything else on the advanced tab...

Is there a way to parametrize WSDL url when we use the web service transformer stage in DataStage?

Thanks Craig! Every record is in the following format: Address1 Address3 Customer1 ---> ---> Customer2 ---> Address2 Address4 Customer2 is a duplicate customer of Customer1. Customer1 has an array of addresses (Address1 and Address2). Customer2 also has an array of addresses (Address3 and Address4)....

I have a requirement that needs me to handle arrays in DataStage before calling a web service. Every record is in the following format: Address1 Address3 Customer1 ---> ---> Customer2 ---> Address2 Address4 (Not sure if the illustration above will be of any help, I have a Customer1 who has an array ...

You can create two separate jobs. The first job splits your data into two files/datasets (One file contains your errors and the second one is your valid records). The second job can be used to load the data into the target. Between the first and the second job you can check to see if the error file ...

In the transformer put in a constraint to check for your error code and set a value for "Abort After Rows"

In the Sequential file stage, you have a property under Options "Read First Rows".

Set the value of this property to a job parameter and you should be good to go.

Can you be a little more specific? What is it you are trying to do?

The keys you partition on in the first join will be different from the keys you partition on in the second join.

What are the various stages in your job?

Like Craig mentioned, you probably have values that are not null in the Salary field. Hence apart from checking for nulls, also check to see if those fields are empty.

Glad to be of help :D

Okay. One of the ways you can achieve this is to do a lookup first (this will depend on your data volumes) Then send the rejects from the first lookup to a second lookup stage where you use the same reference dataset. You can then Funnel the outputs from both the lookup and proceed with any other tr...

Can you please explain a bit more elaborately as to what your requirement is?