Shell script execution

A forum for discussing DataStage<sup>®</sup> basics. If you're not sure where your question goes, start here.

Moderators: chulett, rschirm, roy

qt_ky
Premium Member
Premium Member
Posts: 2895
Joined: Wed Aug 03, 2011 6:16 am
Location: USA

Post by qt_ky »

The point is to check and compare all environment variables during the script execution. Add a line in the script using the set or env commands output to a file. On AIX set always gives more output than env. Run the script from the command line and also from the DataStage job. Add to script:

Code: Select all

set >>~/set.txt
Choose a job you love, and you will never have to work a day in your life. - Confucius
PaulVL
Premium Member
Premium Member
Posts: 1315
Joined: Fri Dec 17, 2010 4:36 pm

Post by PaulVL »

I ran into this sneaky "feature"...

Does your script execute any command whos standard out will be scraped?

Check your COLUMNS setting. I saw that the default COLUMNS setting was that of the shell window setting when the engine was last bounced. It was a small window, so 80 columns was the setting. Messed up a few scripts that anticipated having more.

When tested outside of DataStage, the tester maxed his window so the command worked great.
wahi80
Participant
Posts: 214
Joined: Thu Feb 07, 2008 4:37 pm

Post by wahi80 »

I'm not sure why but after bouncing my server, the job is running fine with the shell script
Post Reply