Datastage internal variable which reset everyday

kcbland · Post by **kcbland** » Mon Apr 28, 2008 11:53 am

Only an environment variable will work reliably and have visibility to all jobs. From a maintenance standpoint this will be easier.

ray.wurlod · Post by **ray.wurlod** » Mon Apr 28, 2008 4:45 pm

Two environment variables, one to store the counter value, the other to store when it was last updated. If that was yesterday or earlier, reset the counter to 1. You can do this readily through a Routine activity or a before-job subroutine.

Tip: store the date in YYYY-MM-DD format or DataStage internal format, and you can compare it directly to today's date without conversion.

swades · Post by **swades** » Tue Apr 29, 2008 10:00 am

Kenneth/Ray,
Thanks for your time,
Coluld you please elaborate more ? Little detail level please ?

Thanks

kcbland · Post by **kcbland** » Tue Apr 29, 2008 10:14 am

How about a shell script that sets the environment variable to 1 every day at 00:00:01? Then, another shell script is run every time you wish that environment variable incremented that simply adds one to the existing value and sets it back.

For Ray's example you'll have a script that set to 1 if the environment variable date isn't today (and updates the date variable to today), otherwise it increments the counter variable. For his you'll need to run the sample script everyday at 00:00:01 to reset the value. His solution would require just one script, whereas the way I suggested requires two.

swades · Post by **swades** » Thu May 01, 2008 5:46 pm

In Dev environment, I created one environmental variable at Project level by DS Administrator, and at Job level I am defining the value of this parameter as $ENV. Also I am executing shell script in Before-job subroutine. It is working fine.