DSXchange

Hi Folks, Just want to borrow your brains. Is there a way to handle errors/exception inside a server routine (DataStage basic)? I have the function below, and it throws a fatal error when the link doesn't exist which make the job abort. Routine name : GetRowCount $INCLUDE DSINCLUDE JOBCONTROL.H hJob...

Does anyone know if there's a parameter at project level to set the File Block Size? I want to reduce the gap between ids generated by the surrogate key generator.

Hi Ernie, sorry I didn't understand your solution. My soap envelope comes from a text file,it's right to go and doesnt have those tags. this is the structure of the job TEXT FILE ------> wbs transformer ------> TEXT FILE Could you elaborate more on how to intercept the message before it goes out to ...

Ernie, the envelope comes from a text file in a column and goes straight into the webservice transformer. As I am using "user defined message", I believe datastage should send the envelope "as is" to the webservice but it's not. It's wrapping up my envelope with additional tags. ...

Hi Ernie, thanks for your help. Yeah, I have server job, and I am using the webservice transformer stage. The job is quite simple: Text file ------>WBS transformer stage -----> text file That message I picked up from the logs. My issue is that datastage is adding tags to my message and I want supres...

Hello Folks, I'd like to borrow your brains for a moment. I am working with soap web service. I'm constructing my own request message (user message) but DataStage keeps adding its tags (Envelope and body) to it making the request unreadable by the web service. Any ideas on how to stop it? This is th...

Hi All, Does anyone know how to get the xml messages composed by the webservice transformer stage and sent to a webservice? I'm trying to debug an error we are getting from a Primavera Webservice. My goal is to get the xml request built by datastage and then try to simulate the same request in other...

Hi Everyone, Just want to get some insights and opinions from the ds developers here. We are currently working on datastage migration from v6.0 to 8.7 and we are about to make a few decisions that would be hard to back out if they turn out to be wrong. The main decision to be made is to wether or no...

Hi Chullet,
Yes, this issue occurs with the new oracle connector. Everything tells me it could be an issue with 8.7 as the same job in 8.5 works welll using the same table - we are doing migration. We have a PMR raised. I'll keep you guys informed.

Hi All, We are migrating datastage jobs from 8.5 to 8.7 and we encountered an issue with Oracle CLOB fields. Has anyone experienced this? The same job in 8.5 runs flawlessly using the same Oracle CLOB fields. Well, I'm not expecting to get answer here, but this an alert that 8.7 may have its own iss...

Hi All, I'm trying to see the XSLT produced internally for a XML file. I've followed what's written in then manual but I didn't manage to get the XSLT content dumped in the job log. What I did was to select subroutine calls in the tracing tab before running the job. Is there anything else to set? My...

Hi Ernie, The address id is set as the key for the repeating group. The issue is not with the repeating group, it's with the absence of attributes. In ds 6.0, it worked fine, absent attributes are created with null content, in version 8.5 columns are created too and random values put in them. We rai...

Hi Folks, We are encontering a problem with xml files that contain nested records (repeating groups). Datastage is pretty much fabricating data for fields that don't appear accross all the records of a repeating group. For example, the file below contains 2 addresses for the customer 55000. The seco...

Hi Vasu,

Could you let us know exactly the environment and versions you have got there?

Found the issue. In the oracle enterprize stage, the table name property had an additional character at the end of the table name. I reckon it was char(13), so I deleted the character and the issue is resolved. I knew it should be something silly.

Thanks anyways.

Cheers