AMQ9213: A communications error for CPI-C occurred.

Problem Description: User getting AMQ9213 when starting sender channel.

Reference: Woloc user

Effected User: Sender channel with SNA protocol in retry status. All sender channels with TCP/IP protocol are in running state.

MQ Version: 5.3 CSD12

OS: Unix

Action: Check /var/mqm/qmgrs/BPDS11/errros/AMQERR01.LOG. The error reads as follows:

-------------------------------------------------------------------------------
11/27/06 13:24:57
AMQ9213: A communications error for CPI-C occurred.

EXPLANATION:An unexpected error occurred in communications.ACTION:The return code from the CPI-C (cmrcv) call was 6 (X'6'). Record these valuesand tell the systems administrator.
-------------------------------------------------------------------------------
11/27/06 13:25:14
AMQ9213: A communications error for CPI-C occurred.

EXPLANATION:An unexpected error occurred in communications.ACTION:The return code from the CPI-C (cmrcv) call was 27 (X'1B'). Record these valuesand tell the systems administrator.
-------------------------------------------------------------------------------
11/27/06 13:25:14
AMQ9999: Channel program ended abnormally.

EXPLANATION:Channel program 'MQS1.BPDS11.INQ.01' ended abnormally.ACTION:Look at previous error messages for channel program 'MQS1.BPDS11.INQ.01' in theerror files to determine the cause of the failure.
-------------------------------------------------------------------------------

2024 MQRC_SYNCPOINT_LIMIT_REACHED Problem

Problem Description: 1200 cyl of DASD has been dedicated to CIF box (NCIF) in MBB1 & another 1200cyl in MBB5. However, during recent batch propagation, we were unable to send even 30,000 rec. The error is 2024 MQRC_SYNCPOINT_LIMIT_REACHED (refer below).

Please explain why we still experience this problem even 1200cyl has been dedicated to CIF?

This limitation is not acceptable as we are processing bulk data. We cannot afford to send 10,000 records at 1 time for 1.2 million customers. 10,000 recs at 1 time is as per previous environment (shared DASD with other application).

Explanation: An MQGET, MQPUT, or MQPUT1 call failed because it would have caused the number of uncommitted messages in the current unit of work to exceed the limit defined for the queue manager (see the MaxUncommittedMsgs queue-manager attribute). The number of uncommitted messages is the sum of the following since the start of the current unit of work:

• Messages put by the application with the MQPMO_SYNCPOINT option
• Messages retrieved by the application with the MQGMO_SYNCPOINT option
• Trigger messages and COA report messages generated by the queue manager
  for messages put with the MQPMO_SYNCPOINT option
• COD report messages generated by the queue manager for messages
  retrieved with the MQGMO_SYNCPOINT option
• On Compaq NonStop Kernel, this reason code occurs when the maximum
  number of I/O operations in a single TM/MP transaction has been exceeded.

Corrective action: Check whether the application is looping. If it is not, consider reducing the complexity of the application. Alternatively, increase the queue-manager limit for the maximum number of uncommitted messages within a unit of work.

Suggestion: If we are confident that the application is not looping and the application does not want to send these messages in smaller batches (reducing the complexity) then by all means increase this value to accommodate there predicted amounts.

Please also check that the Local Q these messages will be delivered to can handle the message total, by IBM default these are set to the highest value.

Maximum queue depth . . . . : 999999999 0 - 999999999

Also for performance you may want to increase the Buffers allocated to the PSID associated to the Local Q that these messages are sent to.