These logs might be on separate machines, and must be used in conjunction with the workbench output to ensure that the deployment was successful.
Use the mqsilist command to check that the deployment was successful, or look in the Windows Event or broker domain Event Log.
If that queue has been accidentally deleted, the broker environment has been damaged, and you must repair it.
See each explanation below of error messages that might be generated during a deployment.
mqsichangeconfigmgr -j 512
alter ql(transmit_queue_name) maxmsgl(104857600)
mqsistop configmgr
mqsistop <broker>
amqmdain end <queue manager>
mqsistart configmgr
mqsistart <broker>
amqmdain start <queue manager>
alter chl(CM_to_BRK) chltype(sdr) MAXMSGL(104857600) alter chl(BRK_to_CM) chltype(rcvr) MAXMSGL(104857600)
alter chl(BRK_to_CM) chltype(sdr) MAXMSGL(104857600) alter chl(CM_to_BRK) chltype(rcvr) MAXMSGL(104857600)
SQL0973N Not enough storage is available in the APP_CTL_HEAP heap to process the statement. SQLSTATE = 57011
This might be because the User Name Server is not started, or the WebSphere MQ channels between it and the broker are not started, or because the user ID is not present in the User Name Server's domain.
TDS Extractor Trace File ======================== Beginning Extract.. Extracting Identification Info Extracting Project Info Extracting Messages Extracting Elements Extracting Compound Types Extracting Type Members Extracting Type Members Extracting Type Members Extracting Type Members Extracting Type Members Beginning Indexing.. Creating Member IDs to Tags Index Table. Beginning Validation.. Validating Project Validating Types ERROR: TDSValidator::ValidateTypeMemberSimpleElement: Simple elements in a type with Data Element Separation attribute = Tagged Delimited must have the following attribute set: Element Level - Tag (Element ID: Town) (Type ID: AddressType) Return Code: -80 Validating Messages Trace Info =========== EXCEPTION: TDSValidator::Validate: TDS Validation failed. 1 errors 0 warnings Return Code: -1
Server already started
+(MQ05BRK) 0 BIP2070E: A problem was detected with WebSphere MQ while issuing MQPUT for WebSphere MQ queue SYSTEM.BROKER.ADMIN.REPLY, WebSphere MQ queue manager QM_01. MQCC=2, MQRC=2030. +(MQ05BRK) 0 BIP2068E: The broker was unable to put an internal configuration message to message queue SYSTEM.BROKER.ADMIN.REPLY.
On the broker queue manager, check the SYSTEM.BROKER.ADMIN.QUEUE. If there are messages on this queue, there might be a broker error; look in the local error log on the broker's system. If the queue is empty, continue with the next step.
Recheck the SYSTEM.BROKER.ADMIN.QUEUE on the broker queue manager. If the queue depth has not increased, there is a problem with the channel between the Configuration Manager and the broker; check the WebSphere MQ logs. If the queue depth has increased to one, continue with the next step.
This allows the broker to process the configuration change and send a response. Wait for the broker to process the message; this could take some time. (If the message takes more than five minutes to process, there is a problem with the deployed message and failure messages appear in the local error log on the broker's system indicating the reason for the failure.) Check the SYSTEM.BROKER.ADMIN.REPLY queue on the Configuration Manager's queue manager. This should contain a response. If it doesn't, check that the channel from the broker to the Configuration Manager is running.
Check that the messages are read from the SYSTEM.BROKER.ADMIN.REPLY queue on the Configuration Manager's queue manager. If they are not, check the local error log on the Configuration Manager's system for errors.
Related concepts
Message flow application deployment
Related tasks
Deploying message flow applications
Are the UNIX environment variables set correctly?
Dealing with problems
Related reference
mqsideploy command
mqsilist (list resources) command
mqsistart command
mqsistop command
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
au16540_ |