| Author |
Message
|
| immaculate |
 Posted: Mon Sep 22, 2014 8:46 am Post subject: how do control-m jobs connects to mq |
 |
|
Novice
Joined: 15 Sep 2014
Posts: 17
|
Application connecting to mq using control-m , and getting following error
=
|Mon 09/12/2014 1:25:01.48| OP-START
|Mon 09/12/2014 1:25:01.48| Delete Already Published Files from D:\i2\op\CET\publish\DEV\request..... START
|Mon 09/12/2014 1:25:01.48| Delete Already Published Files from D:\i2\op\CET\publish\DEV\request...... END
|Mon 09/12/2014 1:25:01.48| Publish to DEV TEST Message Queue ..... START
The system cannot execute the specified program.
|Mon 09/12/2014 1:25:01.50| Publish to DEV TEST Message Queue ..... FAILED
|Mon 09/12/2014 1:25:01.51| OP-ERROR : Exit Unsucessfully with return code# 1
what is this error and how to rectify this.No errors are rec orded in qmgr errors |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Sep 22, 2014 8:50 am Post subject: Re: how do control-m jobs connects to mq |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| immaculate wrote: |
|Mon 09/12/2014 1:25:01.48| Publish to DEV TEST Message Queue ..... START
The system cannot execute the specified program. |
Erm...
| immaculate wrote: |
| what is this error and how to rectify this.No errors are rec orded in qmgr errors |
...it means that the system cannot execute the specified program, probably due to a lack of OS permissions.
No errors are recorded in the queue manager errors because nothing actually ran that went anywhere near the queue manager.
This is not a WMQ problem, but a problem with the OS set up, control-m or both.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Sep 22, 2014 8:51 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
What is "control-m"?
| Quote: |
| The system cannot execute the specified program |
You need to debug your application to determine why its throwing this error code.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Sep 22, 2014 9:09 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Sep 22, 2014 9:13 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| It's possible that ctl-m is trying to run the MQ programs in a shell that does not have setmqenv applied. |
|
| Back to top |
|
|
| immaculate |
| Posted: Mon Sep 22, 2014 9:21 am Post subject: |
|
|
Novice
Joined: 15 Sep 2014
Posts: 17
|
Application has ran control-m jobs for another message for queue DEV1 and it was ran successfully with same configuration like ... O/S , to same server and queue manager.only change is CHANNEL NAME.
could it be any difference. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Sep 22, 2014 9:27 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| immaculate wrote: |
| could it be any difference. |
Unlikely - that's an OS message not an MQ one.
And as you correctly pointed out, there's nothing in the queue manager logs about a failed connection. You can easily test this by setting this control-m job to use a channel name that's previously worked.
If it's the same configuration, is that same configuration executing the same MQ-aware component (either supplied with control-m or externally) in the working as the non-working situation? If so, I'd look into the suggestion of my most worthy associate. If not, I'd see what the differences are in permissions between what control-m executes when it works and what it tries to execute when it doesn't.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
