Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+environment\s+variables\s+cause\s+problem\s+for\s+operational\s+reporting\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+environment\s+variables\s+cause\s+problem\s+for\s+operational\s+reporting\s*$/: 1 ]

Total 1 documents matching your query.

1. [ADSM-L] environment variables cause problem for operational reporting (score: 1): Author: Mehdi Salehi <ezzobad AT GOOGLEMAIL DOT COM>; Date: Mon, 29 Mar 2010 21:54:27 +1000; Hi all, To use operational reporting feature of TSM, I installed the console on my windows client where b/a client already exists. The problem is that console is launched with env variables of b/a cl; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2010-03/msg00389.html (10,699 bytes)

Current List: 1 - 1
Page: [1]