DSXchange

I know its a good idea to set variables to use as connection information, but how do I do that with the password?
Jim

tonystark622 wrote:You might look yourself. It's not outside the realm of possibility that I missed it.

Tony

I beleve we may be working on a work around letting the mg server drop stuff to us in a txt file and then schedualing DS
We will see if that works
Jim

tonystark622 wrote:I didn't see one. I just looked on the Windows install and the HP install disks.

Tony

great no documentation

this seems to be the way my life goes nowadays

With version 7 Ascential added "Real Time Integration" capabilities to DataStage. You can have automatic load balancing between DataStage servers, jobs that can be called as web services (always running), jobs that access Web Services as a data source/target, you can access job status/job...

That's true. I had forgotten the RTI stuff. I wonder if there are any restrictions (like server must be installed on DataStage server) with that? Of course, there is a charge for RTI and none for MQ. Like I said, we worked around it by writing our transactions to an XML file and then running an ext...

hehehehe and ill pull the time to do that out of thin air man u would think that someone at DS would have thought this out....but maybe they did. How do you check kick backs in a company like DS? To their credit, Ascential did mention that we should put in official request for this functionality (t...

When I looked into this for version 6, you had to have to have an MQ Server running on the DataStage server. The MQ client wasn't enough. Can anyone from Ascential comment on this? Has this changed? Jim, We didn't want to incur the cost for MQ Server licensing on the DataStage server because of cos...

You didn't have to host the queue on the DataStage server. The queue could be on another MQ server, and the server on your DataStage server would treat it as a remote queue. But we still would have had pay for licenses for both servers. Tony I just cant beleve that this is the only way. The only er...

When I looked into this for version 6, you had to have to have an MQ Server running on the DataStage server. The MQ client wasn't enough. Can anyone from Ascential comment on this? Has this changed? Regards, Tony Stark Wooooo doggie. That cant be. I dont want to host the que i just want to read fro...

For the MQ plugin to work do I need the MQ Series Client installed on the server?
Jim

The date part needs to be YYYY-MM-DD unless your DBA change local settings. I'm getting "foggy" after programming datastage jobs for 8 hours. Ogmios ohh the world is complete!!!! the bit of knowlage that i needed, the DB2 Date Format!!!!!!!! you are a god man :) thanx Jim maybe tomorow we...

ogmios wrote:The date part needs to be YYYY-MM-DD unless your DBA change local settings. I'm getting "foggy" after programming datastage jobs for 8 hours.

Ogmios

ohh the world is complete!!!! the bit of knowlage that i needed, the DB2 Date Format!!!!!!!!
you are a god man
thanx
Jim

The "am" is not good in time, DB2 is very picky on its input. Try "MTS" for the time part. Ogmios out put of code: 03-01-2004 00:00:00 code: OCONV(ICONV(Exp_Stg_Load.VDATE, "D-YMD[4,2,2]"), "D-MDY[2,2,4]") : " " : oconv(00:00:00, "MTS") St...

Removeing the coma and sending the out put to a flat file gets me the output of: 03-01-2004 12:00:00am using the following code: OCONV(ICONV(Exp_Stg_Load.VDATE, "D-YMD[4,2,2]"), "D-MDY[2,2,4]") : " " : oconv(00:00:00, "MTHS") PS. removing the comma did not alo...

AGGGG I used this line: "2004-05-24" : " " : Oconv("00:00:00","MTHS") and it worked, so that means there is a problem with my oconv inconv. this is my code: OCONV(ICONV(Exp_Stg_Load.VDATE, "D-YMD[4,2,2,]"), "D4-MDY[2,2,4]") so whats up with...