Control-M for z/OS - The Application Server CTMAS fails after CTW004E with RC=222.  ECAB43W and ECAG4LE messages appear in the IOAGATE joblog.

Version 4
Created by Knowledge Admin on Dec 4, 2015 8:03 PM. Last modified by Knowledge Admin on Nov 15, 2019 4:00 AM.
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    Control-M for z/OS


    COMPONENT:

    Control-M for z/OS


    APPLIES TO:

    Control-M for z/OS



    PROBLEM:

     

    CTMAS fails after issuing message CTW004E with Return Code=222. 

      
      CTW004E UPD: MBX INTERNAL ERROR ENCOUNTERED. FUNCTION: WRITE      RC=222

     


    CAUSE:

    Timeout in MBX API - This is an internal API


    SOLUTION:

     

      Here the RC=222 in message CTW004E indicate a timeout.  
      CTW004E UPD: MBX INTERNAL ERROR ENCOUNTERED. FUNCTION: WRITE      RC=222
      

    Getting RC=222 in message CTW004E when writing to a mailbox (MBX) indicates that IOAGATE has not responded to the application server for the MBXTOUT time interval.
    The MBXTOUT is an internal undocumented parameter.
    Its default value is 2 minutes.

    Usually this indicates that IOAGATE and/or CTMAS are not getting enough CPU resources,
    - either because their priority is not high enough
    - and/or because the whole system is experiencing a heavy load.

    The suggestions to fix the problem are to consider:
    - raising the priority of CTMAS and IOAGATE
    - and/or increase the timeout by setting parameter MBXTOUT=3 (or higher) in the APSERVER section of member ECAPARM in the IOA PARM library.
    Task priority is more likely the problem than the timeout interval.

      

    Messages ECAB43W and ECAG4LE are issued by IOAGATE. 
    The 1st is a timeout warning message. 
    The 2nd indicates that CTMAS has failed.
    IOAGATE will automatically restart CTMAS, but popagation of Global Conditions (and possibly other function) may sometimes not resume until IOAGATE has been recycled.

    If the problem persists, cancel IOAGATE with a dump before recycling it, and provide that dump to BMC Technical Support for investigation.

     


    Article Number:

    000084674


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles