IBM STREAMS 4.1.1.1 and 4.1.1.2  JOBS DO NOT INHERIT THE ENVIRONMENT VARIABLES SET IN .BASHRC, WHEN STREAMS IS RUN AS A SYSTEM SERVICE - United States  FLASH (ALERT)

ABSTRACT
 In Streams 4.1.1.1 and 4.1.1.2 Streams jobs may not pick up the user enviroment from the streams user's .bashrc. This behavior is different from earlier releases. With these versions, when Streams is run as a system service, application environment variables must be set with streamtool. 

CONTENT
Problem Description
When running Streams as a system service with Streams releases 4.1.1.1
or 4.1.1.2, toolkits and user applications that depend on the
user environment may have various errors.
For example the database toolkit might show the following error
if it does not pick up the ODBCINI environment variable:



 * "An SQL operation failed. The SQL state is 08003, the SQL code
   is 0 and the SQL message is [unixODBC][Driver
   Manager]Connnection does not exist."
 * 

Problem Solution 

To work around the issue, set environment variables that are needed by the application directly in the instance with:  * 
   
 * streamtool setproperty
 * -d <domain> -i <instance>
   --application-ev <VARIABLE NAME>=<VARIABLE VALUE>
 * 
   


RELATED INFORMATION
 APAR IT18432 [https://www-01.ibm.com/support/entdocview.wss?uid=swg1IT18432]
User environment variables no longer getting picked up after upgrade to 4.1.1.1 or 4.1.1.2? 

Have you found that after upgrade to Streams 4.1.1.1 or 4.1.1.2, that environment variables set in your .bashrc are no longer being set? For example ODBCINI is not set for the database toolkit and you get

     An SQL operation failed. The SQL state is 08003, the SQL code
     is 0 and the SQL message is [unixODBC][Driver
     Manager]Connnection does not exist.

To work around the issue, set environment variables that are needed by the application directly in the instance with:  * 
   
 * streamtool setproperty
 * -d <domain> -i <instance>
   --application-ev <VARIABLE NAME>=<VARIABLE VALUE>