DSXchange

Thank you Craig and Billie(dspxguy) for your response.

Pradeep.

Does anyone know how can we purge Job logs through Unix command line ?

Appreciate your response,
thanks,
Pradeep.

Jagan617 wrote:

Use the latest plugin whatever is available...It's easier, if any upgrades happen on Oracle side in the future....using some of the utilities available in DS we can update the Oracle project accordingly on datastage side too.....

killbill1 wrote:Could someone please let me know till when will IBM be supporting the Datastage 7.5.2 both server and PX versions.

Thanks,

Kill Bill 1

You might want to check this with IBM directly......as I strongly believe no one in DSXchange is supporting IBM...........

Parallel Job with 2 Transformers. About 137 columns using Null to empty, Null to Zero functions in all columns as Transform process. The Job takes 30 mins to compile. Not the case with other similar Jobs with around 50 columns. What are the primary checks I need to see the isuse? Thanks in advance ...

I have certain environment variables set up across all three of my environments on the Datastage Server. There is one Datastage server with a development environment, testing environment, QA environment and production environment. When I export jobs to a DSX file from the development environment an...

Can you be more clear on this.

Then Oconv(Iconv('99991231', "DYMD"),"D-YMD[4,2,2]") : "00:00:00"

If you know how the target date format should be (in case of nulls and blanks)why do you want to use Oconv and Iconv functions.just hardcode it
like "9999-12-31"

ray.wurlod wrote:Double check the location of the file that you have specified in the DSN. Check that you have permission to open the file. Size should not be a problem just to open the file.
...

Also try
the file name is correctly spelled(Do not copy & paste file name...instead try typing it in.)

no biggi......

Take it easy

cheers,

sud wrote:

pradeepleon wrote:Check for the OCONV() function in the help topics.

Parallel jobs, no oconv. Well, you have to actually check this, the timestamp format within datastage IS in 24 hr format, so you should not have to do anything special.

Oh I'm sorry, I thought it to be for a server job.

Check for the OCONV() function in the help topics.

I removed all the stages in the job and directly sourced the data from the source SQL table in to a Seq file. I get the same result. Every character field is of lenght 1 in the file , so if a NAME = Mike , then in the file NAME = M. Try this, Go to the source stage(SQL Server), outputs tab, columns...

abc123 wrote:Yes, I did that already. I was looking for a solution without the transformer for performance reasons.

As John mentioned earlier ,I believe you need an active processing stage to route the data properly.Using any active stage would avoid such warnings.

You need to set a delimiter.....check on that part.