We encountered something similar to this in a product some years ago, where it read the PATH and CLASSPATH variables into a buffer of only 255 bytes. It couldn't see anything in the PATH statement beyond 255 bytes. With long file names, getting longer by the day, it's not long before you've used up all of those precious 255 characters. I'd check with the vendor to see how they treat those environment variables.
| "Thomas, Don"
<[EMAIL PROTECTED]>
Sent by: MQSeries List <[email protected]> 03/02/2005 03:15 PM
|
|
Group,
I have
a pet peeve that maybe one of you can help me with. When
MQ is installed on a Windows server, be it NT or 2000, we all know that
the PATH statement is updated with the appropriate MQ directories.
However, when MQ is not among the first things installed, and the MQ
entries are further down the PATH statement, some applications, Candle
and Microfocus among them, can't seem to find the MQ libraries. I have
to edit the PATH statement and move the MQ entries to the beginning and
reboot the server before these applications can resolve the various .dll
references. Can anyone explain why this is or know of an easier way to
get around this?
Don Thomas
MASC - Coraopolis
Phone:+1-412-893-1659
mailto:[EMAIL PROTECTED]
Instructions for managing your mailing list subscription
are provided in the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
