Greetings,
I have some software installed on a Solaris 10 machine that I am trying to
start with a STAX job. In order to start the software you are required to
source a profile script first to setup the environment.
root# . /path/to/application/profileroot# appControl startServer
My first thought was to just build the environment by hand using the ENV
parameter of PROCESS START however I cannot depend on the environmental
variables always being the same. Also I would prefer to keep the logic of
building the environment in the shell script the application ships with.
I thought perhaps I could use a static handle to tie the processes together,
such as:
C:\> STAF solarisMachine PROCESS START SHELL COMMAND . PARMS
/path/to/application/profile STATICHANDLENAME appEnvironment
Response-----------393
C:\> STAF solarisMachine PROCESS START SHELL COMMAND appControl PARMS
startServer ENV STAF_STATIC_HANDLE=393 WAIT RETURNSTDERR
Response--------{ Return Code: 1 Key : <None> Files : [ {
Return Code: 0 Data : sh: appControl: not found
} ]}
I can tell the environmental variables did not persist between processes as the
PATH appears to be incomplete. This leads me to believe I am misunderstanding
the concept of static handles.
Any thoughts on how I could solve this problem?
- Ryan
------------------------------------------------------------------------------
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today.
http://p.sf.net/sfu/quest-sfdev2dev
_______________________________________________
staf-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/staf-users
