...and quote enclosed the log info etc. _________________ It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys.
The script is being invoked by a BuildForge agent running locally. (This is capturing the output).
If I re-directed the output to a file it'd actually be pretty hard to get at due to firewalls (but BuildForge has been configured for us to have access).
Part of my problem is this occurs periodically and inconsistantly (deploy it again with the exact same version and it works).
I agree that the -v option is a good idea. However I was hoping someone might know what the 255 actually means.
I tried "http://publib.boulder.ibm.com/infocenter/wmbhelp/v7r0m0/index.jsp"
"mqsideploy command"
Which got me:
Quote:
Responses
This command returns the following responses:
0
The command completed successfully.
2
(Failure) The broker received the deployment request but was unable to process it successfully. See the messages issued from the utility (or the Administration log) for more information.
9
(Failure) The request has been submitted to the broker, but no response was received before the timeout expired.
10
(Failure) Another user or application canceled the request operation before the broker was able to process it.
98
The broker is not running.
99
One or more of the parameters that you specified is invalid.
However thats not really that helpful. (I've also discovered that "5" can be returned in the case of a timeout.) which makes me wonder about the accuracy of the infocenter doco.
If it persists I'll be trying the -v. (I would then need to wait for the problem to (randomly) occur again).
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