DSXchange

Hi and Welcome aboard! I think you need to clarify what you are trying to say. Are you suggesting to implement your loading, reference, lookup, staging, mapping and writing phases into one job you might have a maintenance nightmare. Generally smaller components will be easier to manage, although too...

I might go with T42's sort solution. The conceptual design makes sense to me and T42's description should be all that you need to develop this solution. If T42's solution doesn't make sense then I would suggest some training (ask AscentialSoftware).

Yes, this sounds like a security issue to me.

No problem jzparad, we all make silly mistakes at one time or another.

SQL Type: Decimal
Length: 1
Scale: 3

If the length of the column is 1, then where do you expect the remainder to be stored?

Try increasing the length of your column.

Wouldn't you hide the code? No good giving away your hard earned experience to just anybody. Back to your conceptual question: I am almost certain that points 1 & 2 can be designed through a datastage job. 1) This job might look like this: UV stage --> Xfer --> Seq In the UV stage you will need ...

Datastage has the capacity to accomplish your desired result but you have to take a different approach. Any database statement if successful will not return anything in the LOG otherwise the log would always be full of 'successful entries'. On the other hand, if a statement has not successfully comp...

Welcome aboard! I think what you are trying to do is export some information about your existing jobs in a certain project? If so, <a href="http://www.kennethbland.com">Kenneth Bland</a> has some great utilities for this. No point re-inventing the wheel. Register on his site and have a loo...

Perhaps try running the jobs in a Job Sequencer, not as an After Job subroutine.

Just a general comment regarding your post. Sometimes during DS development incomplete jobs and processes that have incomplete or 'dodgy' code in them can lock tables and routines without unlocking them. When this happens to an internal Datastage component you can unlock it by telneting to the DS se...

Shell scripting can be a powerful tool in Datastage, but don't forget about the power of Datastage BASIC. I'm sure there must be a million things that can both be done using either Datastage BASIC or Shell scripting. But becuase DatastageBASIC uses the internal Universe engine wouldn't that make for...

Try to register the plugin in Datastage Manager. If you get an error it could have something to do with permissions. When installing DataStage the Unix root account is used and when running Datastage Manager the DataStage Administrator account (dsadm) is used. Try installing the product as the root ...

I'm assuming you have selected 'ExecSH' in the 'Before Job Subroutine' drop down box. What is exact command you are using in the InputValue text box?

This may not be very efficient but it will work:

First design your job to grab the ORACLE table and export it out into a temporary DB2 table.
Then perform your join in a DB2 stage and output your result set to an ORACLE stage.

If you need to convert the date within Datastage you will need to change the incoming format into internal datastage formatting. Something like this: Oconv(IConv(Arg1[" ",1,3], "D MDY[A,2,4]"), "D-YMD[4,2,2]") This will result in your date coming out as YYYY-MM-DD. If y...