| Author |
Message
|
| belchman |
 Posted: Thu Feb 04, 2010 5:21 am Post subject: |
 |
|
Partisan
Joined: 31 Mar 2006
Posts: 386
Location: Ohio, USA
|
Go Figure! I followed the guidance of the manual and it worked.
I moved everything from receive exit to message exit and all is good.
Sorry for wasting you time. 
_________________
Make three correct guesses consecutively and you will establish a reputation as an expert. ~ Laurence J. Peter |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Thu Feb 04, 2010 6:05 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Thank you for doing the basic research on this. Your/our time is not wasted by doing r&d.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| belchman |
| Posted: Thu Feb 04, 2010 10:32 am Post subject: |
|
|
Partisan
Joined: 31 Mar 2006
Posts: 386
Location: Ohio, USA
|
Using this content of file named 'mlconfig.sigcard'...
#
LOCAL_QMGR_NAME="QAQM1"
#### MQ channel names and types ####
set -A CHANNEL_NAMES \
"MQU1.HDB.QAQMAS" \
set -A CHANNEL_TYPES \
"RCVR" \
#### Log files and options parameters ####
set -A LOG_FILES \
"sigcard.#N.log" \
set -A LOG_OPTIONS \
"0,2,5,6,11" \
#### Other parameters ####
set -A OTHER_PARAMS \
"LC=3;LS=5" \
set -A DESCR_PARAMS \
#### General exit parameters ####
# If values are specified, the PARAMETER_FILES array overrides the
# LOG_FILES, LOG_OPTIONS, OTHER_PARAMS and DESCR_PARAMS array settings
set -A PARAMETER_FILES \
#
# End of mlutil configuration
#
When I run ./mlutil sigcard enable, I keep getting the error shown.
$ ./mlutil sigcard enable
MQ commands to be run on Queue Manager 'QAQM1' :
* Enable the message logging exit on the MQ channels
ALTER CHL('MQU1.HDB.QAQMAS') CHLTYPE(RCVR) +
MSGEXIT('wmqcml64.so(wmqcml)') +
MSGDATA('LF=sigcard.#N.log;LO=0,2,5,6,11;LC=3;LS=5;')
5724-H72 (C) Copyright IBM Corp. 1994, 2005. ALL RIGHTS RESERVED.
Starting MQSC for queue manager QAQM1.
: * Enable the message logging exit on the MQ channels
1 : ALTER CHL('MQU1.HDB.QAQMAS') CHLTYPE(RCVR) +
: MSGEXIT('wmqcml64.so(wmqcml)') +
: MSGDATA('LF=sigcard.#N.log;LO=0,2,5,6,11;LC=3;LS=5;')
AMQ8555: String List String Length Error.
:
One MQSC command read.
One command has a syntax error.
All valid MQSC commands were processed.
I have moved things around to try to get that ';' off the end of the MsgData property value. Am I a knucklehead or is it a bug?
_________________
Make three correct guesses consecutively and you will establish a reputation as an expert. ~ Laurence J. Peter |
|
| Back to top |
|
|
| belchman |
| Posted: Thu Feb 04, 2010 12:13 pm Post subject: |
|
|
Partisan
Joined: 31 Mar 2006
Posts: 386
Location: Ohio, USA
|
|
| Back to top |
|
|
| belchman |
| Posted: Thu Feb 04, 2010 12:23 pm Post subject: |
|
|
Partisan
Joined: 31 Mar 2006
Posts: 386
Location: Ohio, USA
|
I manually put
LF=sigcard.#N.log;LO=0,2,5,6,11;
LC=3;LS=5;
for Message Exit data on the channel using Eclipse Explorer v7 and I could do it but it had to be on two lines as shown above.
It works too. Now to figure out how to enter 2 lines from the .config file
_________________
Make three correct guesses consecutively and you will establish a reputation as an expert. ~ Laurence J. Peter |
|
| Back to top |
|
|
| belchman |
| Posted: Thu Feb 04, 2010 1:01 pm Post subject: |
|
|
Partisan
Joined: 31 Mar 2006
Posts: 386
Location: Ohio, USA
|
One more post then I am done for the day...
I am confused why I would see a log file this size
$ ls -la *.log
-rw-r--r-- 1 mqm mqm 78578583 Feb 4 15:48 sigcard.1.log
if I have this in my message exit data property
LF=../qmgrs/QAQM1/sigcard.#N.log
LC=3;LS=5
LO=0,2,5,6,11;
_________________
Make three correct guesses consecutively and you will establish a reputation as an expert. ~ Laurence J. Peter |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Thu Feb 04, 2010 3:16 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
That limitation applies to the total length of exit names and their user data when multiple exits (possibly of multiple types send/receive/message) are defined and they are chained in sequence.
The limit on user data for each exit in the chain is 32 characters.
_________________
Glenn |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Thu Feb 04, 2010 3:23 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| belchman wrote: |
I manually put
LF=sigcard.#N.log;LO=0,2,5,6,11;
LC=3;LS=5;
for Message Exit data on the channel using Eclipse Explorer v7 and I could do it but it had to be on two lines as shown above.
It works too. Now to figure out how to enter 2 lines from the .config file |
It looks like you defined some message exit data for the first exit in the sequence (LF=sigcard.#N.log;LO=0,2,5,6,11;) and the second exit in the sequence (LC=3;LS=5; ).
I don't think this is what you intended to do. Normally wmqcml will be the one and only message exit defined on a channel, and will only have one message exit data associated with it (32 chars max).
If you want to used more than 32 chars of parameters for wmqcml, there are two choices:
1) Extend into the DESCR attribute (using + in the MSGDATA), or if this is not acceptable,
2) Put them in a parameter file (using PF= in the MSGDATA)
BTW, a ";" on the end of the parameters is ignored by wmqcml. The mlutil script puts it there. It just makes the code in the script a bit simplier.
_________________
Glenn |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Thu Feb 04, 2010 3:26 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| belchman wrote: |
...
if I have this in my message exit data property
LF=../qmgrs/QAQM1/sigcard.#N.log
LC=3;LS=5
LO=0,2,5,6,11; |
Is looks like you defined 3 lines of message exit data. That won't work as you think, see my previous post.
_________________
Glenn |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Thu Feb 04, 2010 3:31 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| belchman wrote: |
...
$ ./mlutil sigcard enable
MQ commands to be run on Queue Manager 'QAQM1' :
* Enable the message logging exit on the MQ channels
ALTER CHL('MQU1.HDB.QAQMAS') CHLTYPE(RCVR) +
MSGEXIT('wmqcml64.so(wmqcml)') +
MSGDATA('LF=sigcard.#N.log;LO=0,2,5,6,11;LC=3;LS=5;')
5724-H72 (C) Copyright IBM Corp. 1994, 2005. ALL RIGHTS RESERVED.
Starting MQSC for queue manager QAQM1.
: * Enable the message logging exit on the MQ channels
1 : ALTER CHL('MQU1.HDB.QAQMAS') CHLTYPE(RCVR) +
: MSGEXIT('wmqcml64.so(wmqcml)') +
: MSGDATA('LF=sigcard.#N.log;LO=0,2,5,6,11;LC=3;LS=5;')
AMQ8555: String List String Length Error.
:
One MQSC command read.
One command has a syntax error.
All valid MQSC commands were processed.
I have moved things around to try to get that ';' off the end of the MsgData property value. Am I a knucklehead or is it a bug? |
"AMQ8555: String List String Length Error."
The mlutil script does not check the MSGDATA length. If your combination of parameters is too long, use the documented methods of putting some of them elsewhere.
mlutil is not intended to be a comprehensive script that covers all possible requirements. If its not suitable for you, just revert to using a good old fashioned hard-coded runmqsc command file.
_________________
Glenn |
|
| Back to top |
|
|
| belchman |
| Posted: Fri Feb 05, 2010 4:38 am Post subject: |
|
|
Partisan
Joined: 31 Mar 2006
Posts: 386
Location: Ohio, USA
|
Thanks Glenn,
Let me work with the info you provided.
_________________
Make three correct guesses consecutively and you will establish a reputation as an expert. ~ Laurence J. Peter |
|
| Back to top |
|
|
| burhanali |
| Posted: Thu Jun 13, 2013 3:27 am Post subject: ma0z - HP-UX error |
|
|
Newbie
Joined: 13 Jun 2013
Posts: 1
|
Hi Glenn,
I hope you are doing well.
I have tested ma0z with IBM WMQ 7 on windows, it is working fine. But I received the following error when I deployed ma0z on HP-UX IBM for WMQ 6.0.2.10 follow the user guide,
HP-UX detail: B.11.31 U ia64 3419765867 unlimited-user
06/13/13 14:24:24 - Process(9392.14) User(mqm) Program(amqrmppa_nd)
AMQ6175: The system could not dynamically load the shared library
'/var/mqm/exits64//wmqcml64.sl'. The system returned error message
''/var/mqm/exits64//wmqcml64.sl' is not a valid load module: Bad machine type'.
The queue manager will continue without this module.
EXPLANATION:
This message applies to UNIX systems. The shared library
'/var/mqm/exits64//wmqcml64.sl' failed to load correctly due to a problem with
the library.
ACTION:
Check the file access permissions and that the file has not been corrupted.
----- amqxufnx.c : 1174 -------------------------------------------------------
06/13/13 14:24:24 - Process(9392.14) User(mqm) Program(amqrmppa_nd)
AMQ9535: User exit not valid.
EXPLANATION:
Channel program 'MLIVT.CLIENT' ended because user exit 'wmqcml64.sl(wmqcml)' is
not valid.
ACTION:
Ensure that the user exit is specified correctly in the channel definition, and
that the user exit program is correct and available. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Mon Jun 17, 2013 3:27 pm Post subject: Re: ma0z - HP-UX error |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| burhanali wrote: |
Hi Glenn,
I hope you are doing well.
I have tested ma0z with IBM WMQ 7 on windows, it is working fine. But I received the following error when I deployed ma0z on HP-UX IBM for WMQ 6.0.2.10 follow the user guide,
HP-UX detail: B.11.31 U ia64 3419765867 unlimited-user
06/13/13 14:24:24 - Process(9392.14) User(mqm) Program(amqrmppa_nd)
AMQ6175: The system could not dynamically load the shared library
'/var/mqm/exits64//wmqcml64.sl'. The system returned error message
''/var/mqm/exits64//wmqcml64.sl' is not a valid load module: Bad machine type'.
The queue manager will continue without this module.
... |
Hi burhanali, I am well.
The exit is only supported for HP-UX on PA-RISC hardware, as listed in section 1.5 of the User Guide. Since the User Guide was published, the only additional support has been Linux on x86 64 bit.
_________________
Glenn |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Jun 18, 2013 5:14 am Post subject: Re: ma0z - HP-UX error |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| gbaddeley wrote: |
| The exit is only supported for HP-UX on PA-RISC hardware, as listed in section 1.5 of the User Guide. Since the User Guide was published, the only additional support has been Linux on x86 64 bit. |
I suspect it's not supported for MQ v6 on any platform, either... |
|
| Back to top |
|
|
|
|
