Hi All
I must be missing something here!
I was going to post this question sometime, so it may
as well be now......
I am looking for a way of containing variables so that
they can not be seen globally. The oposite of this
posting.

I want to preserve the original environment and
automatically delete all the work variables created in
a command file. I thought that by going down a CI
level I would isolate the original level's
environment, as in UNIX.


This is the effect I was looking for:
!
!setvar _xx "Original value"
!showvar _@
_XX original value
!xeq command.file
..ci
..setvar _xx "temp value"
..setvar _yy "another value"
..showvar _@
.._XX = temp value
.._yy = another value
..exit
!showvar _@
_XX original value

But the result of the final "!showvar _@" is
_XX = temp value
_yy = another value

Any suggestions please.
And what is a good use for going down another CI
level?

Sorry if these are niave questions, but no one here
seems to know.
Thanks
John Edwards





--- Boris Kortiak <[log in to unmask]> wrote:
> See :HELP SETVAR
>
> >>> JPS <[log in to unmask]> 12/23/99
> 11:11AM >>>
> Hello everybody,
>
> Does anyone know a ci command to do export.
>
> In shell, it's easy
> export variable
>
> But in Mpeix ?
> How to transmit a variable to a job ?
> I could make a mix of shell and mpeix, but I'm sure
> there is something
> better.
>
> T.I.A.
>
> [log in to unmask]
>



__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://messenger.yahoo.com