hi,
can anyone help me in creating a new environment variable using perl, ??

Sure, can you be a bit more specific though, ie give me an example.
You can add to the built-in Perl hash %ENV. See http://perldoc.perl.org/Env.html

thanks for u r support,
hope this will explain to u better
when i use this in my perl script,
system("FLEXLM_TIMEOUT =500000");


I am not able to create an env variable by name FLEXLM_TIMEOUT , after running the script , i checked in env , but the environment variable was not there,pls help

That's because system() creates a new sub-shell, same as if you ran a shell prg.
As you (should) know, you can export env vars down a process tree, but not up.
You could tell it to print the value which would enable a a calling shell to use it.
Here, I mean print from the Perl level, not from within the system() cmd.
See http://perldoc.perl.org/functions/system.html

ok can u tell me anyother way in perl where i can create my own environment variable , and i can access it , pls

Like I said, you can do it that way, but after a script has finished, the (sub)shell in which it runs is removed/destroyed by the OS.
You can save/print it to a temp file.
What exactly are you trying to achieve?

the thing i want to achieve is , i want to create my own environment variable and store it env hash , later env variable is accessed by other scripts,

but if i do as u told ie storing the variable in a tmpfile,

then i have to use that tmpfile in every program which uses that env variable ...

ie require tmpfile;

I think thats not suitable for me , any suggestions ??

-------------------------
regards,
san
FREE as in FREEDOM thats life

Well, a prog can only affect it's own env. If you want to share values with other scripts, you can

1. Call other script from yours and pass value as cmd line arg
2. Call other script from yours and export val to new env eg system("export $var && run_new_script");
3. Use temp file
4. Use threads
5. use fork()
6. use shell and capture / fwd val on cmd line eg
#!/bin/bash
var=$(1st perl script) where script prints val to current env and is captured in $var
run_2nd_script $var
7. use a DB
8. use sockets.

As I mentioned above, progs either run in their own env and/or create a new env to output to.
There is not 1 global env shared by all you progs.
Values can be exported 'down' the process tree but not up.
It's a fundamental design thing with Unix.

HTH