All user created CI variables are global to the job or session
in which the variable been set.  Any process in a job or session
has full access to any variable created in any other process
inside the SAME job/session.

A job directly executing a script (or UDC) is doing so in the
context of the same process.  That is, the CI does not create
a new process to execute a script.  Once a job terminates, the
variables created within that job are deleted.  Perhaps, the
scripts you are referring to where executed inside a different
job?

My comments above pertain to CI variables.  POSIX shell variables
are local in scope unless explicitly exported.

regards,
Jeff Vance, CSY


> I'm troubleshooting a monitoring job that executes numerous
> command files
> and is then supposed to check the results of variables that
> the command
> files set before they died.  The problem I am running into is
> that the job
> does not see the variables that are being set by the command
> files.  I can
> run the command file and after it dies I can still see the
> variables that it
> sets.  Why would it be different with a job?  As I understand
> it, in Unix a
> parent process has to export a variable for its child
> process's to see it.
> Could it be that I am running into something similar (in reverse).