| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| SCYDATA and 32 char limit |
« View previous topic :: View next topic » |
| Author |
Message
|
| PeterPotkay |
 Posted: Mon Jan 04, 2010 1:10 pm Post subject: SCYDATA and 32 char limit |
 |
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
In an H.A. environment the path to where your shared data lives is quite long to begin with if you followed MC91 standards.
/MQHA/MyQMName/data/...
We're at 20 characters before we even start. Add a dir and a file name and its longer than 32 chars quick. So I end up putting my file that SCYDATA references on both nodes of the hardware cluster in var/mqm/exits64. And now I have twice as much work anytime I need to make a change. What a pain in the keister.
I could've sworn I once saw something that allowed you to reference a location longer than 32 characters in SCYDATA using 32 chars or less. Maybe some environment variable or something. Anyone know what that is? Or am I imagining it?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
 |
| RogerLacroix |
| Posted: Thu Jan 07, 2010 2:47 pm Post subject: Re: SCYDATA and 32 char limit |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
Hi Peter,
| PeterPotkay wrote: |
| my file that SCYDATA references on both nodes of the hardware cluster in var/mqm/exits64 |
A while ago, I added support both absolute and relative paths for my products (MQAUSX, MQSSX and MQISD).
When MQAUSX parses the SCYDATA field, MQAUSX can accept the IniFile info as either absolute path ("/var/mqm/exits64/myinifile.ini") or relative location to the "mqausx" shared library ("myinifile.ini").
i.e.
SCYEXIT=/really/long/path/MQHA/MyQMName/data/mqausx(SecExit)
SCYDATA=myinifile.ini
MQAUSX will look for the file in the following directory: /really/long/path/MQHA/MyQMName/data/
Note: The MQAUSX client-side security exit does support MQAUSX_HOME environment variable. If a customer wanted it, then it could be added to the server-side security exit. The customer would have to act quickly as the dead-line for changes has already past (v1.5.0 is due out next week).
Regards,
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Jan 08, 2010 12:18 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Thanks, I knew I saw it somewhere.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Mon Jan 18, 2010 1:05 pm Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Jan 18, 2010 1:13 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
I'll take advantage of this when I upgrade MQAUSX to 1.5 which I'll do as I upgrade my MQ servers to MQ 7.0.1 from MQ 6.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
