nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Set Environment variable in workflow

Srinivasa Talla

Existing code of a task(.ipl file) in a workflow in 5.5.2 is

BEGIN { $ENV{NLS_LANG} = "AMERICAN_AMERICA.UTF8"; }
$ENV{TEMP} = 'C:/TEMP';
$ENV{SYSTEMROOT} = 'C:/WINNT';
$ENV{ORACLE_HOME} = 'C:/oracle/920';

But if I have this code in same task in same workflow in 6.5, if a task is defined , it is always becoming invalid task.
If I comment these lines, there is no problem. Any change in 6.5?

Edited by raot on 10/03/05 11:15 AM (server time).

Find more posts tagged with

Comments

Bill Klish

The version of perl has changed in TeamSite 6.5. I believe TeamSite 5.5.2 had perl v 5.003, while 6.5 ships with perl 5.8 or 5.6 (forgetting now). Have you verified that this .ipl file's syntax is still valid using iwperl -c <your ipl file> ?

Adam Stoller

Shouldn't that be: BEGIN {
$ENV{NLS_LANG} = "AMERICAN_AMERICA.UTF8"; }
$ENV{TEMP} = 'C:/TEMP';
$ENV{SYSTEMROOT} = 'C:/WINNT';
$ENV{ORACLE_HOME} = 'C:/oracle/920';
};
And it's Perl 5.8.2 in TeamSite 6.5

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Srinivasa Talla

thanks fish, so wrong syntax.
But still this statement is giving error..(TeamSite 6.5 sp1, win 2003)

$ENV{SYSTEMROOT} = 'C:\WINNT';

This line causing error "Could not connect to IWSERVER". Anything change in new perl?

Adam Stoller

Where is TeamSite installed on your system?
If you go to your basic command prompt on that server and type:

echo %SYSTEMROOT%

what is the result?

Are you sure that one line is causing the problem?

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Srinivasa Talla

Fish, I got it, thanks for immediate reply.

$ENV{SYSTEMROOT} = 'C:\WINNT'; // win 2000

$ENV{SYSTEMROOT} = 'C:\WINDOWS';//win 2003
For my new OS, the second statement is correct.

That means, Perl trying to set the value of environement variable and try to see its validity?

Adam Stoller

My guess is it means something in the script was attempting to make use of that environment variable in a manner that when it failed to represent the correct path resulted in the error message you saw.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com