DFHZC4951 E `date` `time` `applid` An error has been detected when processing an`{ unknown |` `inbound |` `outbound}` Connection Quiesce Protocol request. Transaction `tranid` is`{ continuing. |` `terminating. |` `terminating abnormally.}` Error code: `X'xxxxx'` Connection: `yyyy`


    Explanation
      An error has been detected during the execution of transaction tranid. The error code indicates the nature of the error:

      
          X'01'

          
            Transaction tranid was not started by terminal input, nor by an internal CICS command.

          
          X'02'

          
            Transaction tranid was started by an inbound FMH5, but the TPN was not the correct value for the Connection Quiesce Protocol.

          
          X'03'

          
            Transaction tranid issued an unsuccessful communications request on an APPC session.

          
          X'04'

          
            Transaction tranid has been attached by an inbound FMH5. The format of the data received from the remote system did not comply with the architecture for the Connection Quiesce Protocol.

          
          X'05'

          
            Transaction tranid has received an unexpected response from the Recovery Manager.

          
          X'06'

          
            Transaction tranid has been attached by an internal CICS command and has sent a Connection Quiesce Protocol request to the remote system. The format of the reply received from the remote system did not comply with the architecture for the Protocol.

          
          X'07'

          
            Transaction tranid was started, but its principal facility is not a terminal or session.

          
    System action
      Depending upon the nature of the event that gave rise to the message, the transaction continues execution, terminates normally, or terminates abnormally. The message text indicates which action is being taken.

    
    User response
      This depends upon the error code:

      
          X'01, 02, 07'

          
            Ensure that transaction tranid was started by CICS-supplied code, and not by application code. If it was started by CICS-supplied code, contact your IBM Support Center.

          
          X'03'

          
            Determine why the communications request on the APPC session failed. Possible reasons are:

            
                There has been a session failure.

              
                The connected transaction has abended.

              
            :pc.This error produces an exception trace, which helps to determine the cause of the problem.

          
      In other cases, contact your IBM Support Center.

    
    Module
DFHCLS5

    XMEOUT parameters/Message inserts
      
      
          date
        

          time
        

          applid
        

        Value chosen from the following options:

              
                1= unknown, 
              

                2= inbound, 
              

                3= outbound
              

          tranid
        

        Value chosen from the following options:

              
                1= continuing., 
              

                2= terminating., 
              

                3= terminating abnormally.
              

          X'xxxxx'
        

          yyyy
        

    Destination
      
      CSNE

DFHZC4951 E date time applid An error has been detected when processing an{ unknown | inbound | outbound} Connection Quiesce Protocol request. Transaction tranid is{ continuing. | terminating. | terminating abnormally.} Error code: X'xxxxx' Connection: yyyy

Explanation

System action

User response

Module

XMEOUT parameters/Message inserts

Destination

DFHZC4951 E `date` `time` `applid` An error has been detected when processing an`{ unknown |` `inbound |` `outbound}` Connection Quiesce Protocol request. Transaction `tranid` is`{ continuing. |` `terminating. |` `terminating abnormally.}` Error code: `X'xxxxx'` Connection: `yyyy`