Datastage/390 is not unable to use CURRENT DATE in the looku

Post by **admin** » Wed Aug 22, 2001 10:42 pm

Hello,

I am just wondering has anybody encountered a situation where you have to use the DB2 CURRENT DATE function to compare against dates.

I have created a RELATIONAL STAGE in the Datastage Designer and I am trying to add two conditions in the WHERE tab to limit selection to those records that have effective date >= CURRENT DATE and termination date < CURRENT DATE. When I tried to verify it, it prompts me for an INVALID WHERE clause.

CURRENT DATE is supposed to be a system date function of DB2 and I am just surprised why it is not accepted in the datastage RELATIONAL STAGE.

Can anybody give me some directions?

Cheers,
Paul Ko.

Post by **admin** » Thu Aug 23, 2001 7:17 pm

Try CURRENT_DATE (add the underscore). That works (at least in version
4.2.1)

Rich

-----Original Message-----
Date: Thu, 23 Aug 2001 10:42:24 +1200
To: datastage-users@oliver.com
From: Paul Ko
Subject: Datastage/390 is not unable to use CURRENT DATE in the lookup sta
ge
Message-ID:

Hello,

I am just wondering has anybody encountered a situation where you have to use the DB2 CURRENT DATE function to compare against dates.

I have created a RELATIONAL STAGE in the Datastage Designer and I am trying to add two conditions in the WHERE tab to limit selection to those records that have effective date >= CURRENT DATE and termination date < CURRENT DATE. When I tried to verify it, it prompts me for an INVALID WHERE clause.

CURRENT DATE is supposed to be a system date function of DB2 and I am just surprised why it is not accepted in the datastage RELATIONAL STAGE.

Can anybody give me some directions?

Cheers,
Paul Ko.