DSXchange

Only solution i can come up with is kind of ugly. its making a comparison of the original date string with the iconv/oconv version. The original will be 2002-02-30 and the iconv/oconv version will be 2002-03-02 so since they are no longer the same, it cant be a correct value. Is this the best (only)...

How do i validate my dates in DataStage ? No matter what i do it seems to accept 2002-02-30 as a valid date. It thinks its 2002-03-02 ( Ive tried Iconv / Oconv Ive tried the SDK DateGenericIsDate Ive tried the code that DateGenericIsDate is using (DateGenericToTimeStamp (%InputDate%, 0)) They all fa...

This is a topic for an orphaned message.

We have been using 6.0 for a few months now with the same configuration (AIX/XP) as well as AIX/W2k. if given a choice, Id still stick with W2K, the client seems to work about 95% correctly on XP. The problems are all cosmetic, but I find them quite annoying (display fonts not correct, the drop-down...

Were currently running the 5.2r1 client on Windows XP Pro and Ive been testing the 6.0 release, with no issues in either case. In order to check for version availability, go to Ascentials eServices website and click on the Product Availability link,, or go there directly: m There you input your serv...

Has anyone got any experience of running the DataStage client version 6.0.R3 on Windows XP? Previous messages tell me that version 5 of the client does not work well on XP. Is this still the case on 6? The server environment is AIX Unix. Also, is 6.0 Release 3 the latest release of DataStage? Thanks...

Hello Tracy, One thing that might cause this problem is active stage "row buffering". I cannot remember at what release this feature first became available - it may have been after 4.1. However, in release 6 there are two places where this can be set. One is in administrator to set a server wide def...

Has your Informix database been installed without logging? If so, it will not support transactions (which would give rise to the message you received which can safely be ignored). If your Informix database has been installed with log, check that the space for the log has not become full. Though in t...

One difficulty with this form of CATALOG is that a copy of the routine is placed in the global catalog directory (GLOBAL.CATDIR) and not subsequently updated. Therefore, if you upgrade DataStage and do not re-catalog the routine, you continue to use the previous version. This can be avoided if the L...

Martin If that works then cataloging local would work even better. CATALOG DSG_BP KeyMgtGetNextValue.B LOCAL Then CALL KeyMgtGetNextValue.B(Ans,Arg1) is cleaner. Thanks Kim. Kim Duke DsWebMon - Control DataStage from the web www.duke-consulting.com -----Original Message----- From: battalio@dataWareh...

Hello One way to access this sub routine is to catalog it. I logged into my project "xmartin" (via the Administrator) and issued the following Command: CATALOG DSG_BP KeyMgtGetNextValue.B It returned: "*xmartin*KeyMgtGetNextValue.B" cataloged. Inside datastage manager I wrote the following: CALL "*x...

This is a topic for an orphaned message.

Thank you Tommy. Leonid "Tommy Chang" cc: Subject: RE: Datastage warning 01/07/2003 04:02 AM Please respond to datastage-users Hi Leonid, SInce ur informix database was created without log, it doesnt support transcation. Just ignore that. Its ok. Br. Tommy -----Original Message----- From: lfrumke@se...

p.s. I am aware that the ErrorCode variable has to be set, this was just originally advice as to the possible reason for the job aborting. It could be that the routine had been modified to set the ErrorCode. ----- Original Message ----- From: "Simon Fryett" To: Sent: Tuesday, January 07, 2003 11:56 ...

Actually I will correct myself here, it is good practice to have all the before / after in the same folder. To ensure they on the list you have to set the routine type to before after. Sorry noticed once sent that this was misleading .... ----- Original Message ----- From: "Simon Fryett" To: Sent: T...