Jim Killam ([log in to unmask]) wrote:
: We have run into a situation where we have a batch job (this job is always
: running) that launches a couple of son processes (say A and B). If A finds or
: causes an error, the value of HPCIERROR (if I remember that is what it is
: called) is set, but then B is processing and checks the value of this
: variable and finds an error has occured (because of A) and while they are not
: related, thinks it has an error and does some type of error handling. Rather
: than sharing this system variable, is anyone aware of a way to let A and B
: have their own unshared value for HPCIERROR (Or any system variable)?
 
The short answer is No.  All CI variables are shared throughout the
job/session tree.  However, it should be relatively straightforward to
concoct a co-operative naming convention which would keep Proc A and Proc B
from tripping over each other's variables.  It could be as easy as
PROCAVAR1 and PROCBVAR1.
 
But if you're referring specifically to HPCIERROR (or any other HP
pre-specified variable), the above scheme won't work.
 
-Larry "what! me CI?" Byler-