Scribd
Upload
101 views3 pages

NDS MQ Series Issues/ Problems/ Errors: Unexpected Error AMQ4048

This document outlines several common problems encountered with the NDS MQ Series, including sender channels in a retrying/binding state, unexpected errors, receivers not starting, and non-zero queue depths. The solutions provided include checking connectivity, stopping and restarting queue managers and channels, clearing messages from queues, and running batch files to process messages in the queues.

Uploaded by

Kishore Krishna
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
101 views3 pages

NDS MQ Series Issues/ Problems/ Errors: Unexpected Error AMQ4048

This document outlines several common problems encountered with the NDS MQ Series, including sender channels in a retrying/binding state, unexpected errors, receivers not starting, and non-zero queue depths. The solutions provided include checking connectivity, stopping and restarting queue managers and channels, clearing messages from queues, and running batch files to process messages in the queues.

Uploaded by

Kishore Krishna
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 3

NDS MQ Series Issues/ Problems/ Errors

1. Problem: Sender Channel in Retrying/Binding State.

Occurrence: Unable to bring the sender channel in Running status by right


click and start

Solution 1. Ensure that the member is able to physically ping to RBI


server from dos prompt (Open Command prompt and execute
command C:\>ping 10.21.1.45 t).
In case it is not able to ping and gives response as request timed
out, please check your leased line/VSAT connectivity.
In case you get regular ping response, carry out following
sequentially on sender channel (by right click on sender
channelall task---followed by):
2. Stop the sender channel. Channel status should change to
stop.
3. Resolve (with option backout). It should give a message that
channel resolved successfully.
4. Reset (option message sequence number 1)
5 Ping. It should give a message that channel was pinged
successfully.
6. Start the channel. The sender channel status should change
to Running.

2. Problem Unexpected Error AMQ4048

Occurrence When trying to Ping the Sender channel through MQ series


(refer above).

Solution Stop all the Queue managers and then start only the NDS1P
queue manager and then start the sender channel. It should
work. Then you may restart the other queue managers. If it
does not work, you may consider rebooting the server (if
possible) or may contact your MQ Series vendor

3. Problem Receiver channel not starting while sender channel is in


Running status

Occurrence When clicking the Question Mark on NDS Server admin screen
to start the Receiver channel

Solution 1.Ensure that the Listener of NDS1P queue manager is


running. (Listener can be checked by right clicking the NDS1P
QMGR and going to Services. Listener can be started or
stopped by right click start/ stop on the listener)

1
2. Stop all the Queue managers and then start only the NDS1P
queue manager.
If the above does not work, call up NDS Helpdesk.

4. Problem Current Depth of UnprocQ is Non Zero

Occurrence Observed when checking the Current Depth of queues on


server.

Solution Run the Unproc.bat file from the following location (in case
you are not having it already, please prepare it as stated below
under Remarks and save it in the stated folder)
C:\Program Files\RBIPDONDSSetUp\StartUp

Remarks The command in the Unproc.bat batch file is PollOnMsg.exe


NDS1P.HL.<LUDID>.UNPROCQ NDS1P.HL.<LUD
ID>.TEMP_UNPROCQ NDS1P.<LUDID>.QMGR
(where <LUDID> is the member's respective Lud ID).

5. Problem Current Depth of TEMP_ UnprocQ is Non Zero

Occurrence Observed when checking the Current Depth of queues on


server.

Solution Check the box 'Process Messages from UnprocQ' on the NDS
Server Admin screen (check box is under the process tabs.
Check it by clicking on the small white square check box).

6. Problem Current depth in the Input Log queue/ Output Log queue is
10000 or near about 10000.

Occurrence Observed when checking the Current Depth of queues on


server.

Solution Clear messages from concerned queue as 10000 is the upper


limit for said queue and once it reaches the limit, NDS message
flow will be affected.
Disconnect and Stop processes on the NDS Server
Administration Screen and then right click the Input Log
queue/ Output Log queue--- All Task ---Clear messages.
Current depth will come down to zero.
NDS server may again be connected and the processes started.

7. Problem Current Depth of TXN Q is Non Zero

Occurrence Observed when checking the Current Depth of queues on


server.

Solution 1) Disconnect and stop processes on the NDS Server Admin


GUI screen. Then again connect and start processes. Refresh

2
the TXN Q continuously. The current depth may initially
increase then it should come down to zero.
2) In case the current depth in TXN Queue is huge (in
hundreds) then it may take time to process messages from
TXN Q. To expedite the processing of messages from TXN Q,
run the POLLON_TXN.bat file from the following location
(in case you are not having it already, please prepare it as stated
below under Remarks and save it in the stated folder)
C:\Program Files\RBIPDONDSSetUp\StartUp.
More than one batch files (POLLON_TXN.bat) can be run
simultaneously. Each running batch file will open a separate
Dos Prompt window.

Remarks The command in the POLLON_TXN.bat batch file is


PollOnMsg.exe NDS1P.HL.<LUD ID>.TXN
NDS1P.HL.<LUD ID>.UNPROCQ NDS1P.<LUD
ID>.QMGR
(where <LUD ID> is the member's respective Lud ID).

You might also like