Unable to create gateway for Control-M for z/OS in the Control-M Configuration Manager. Explanation of what ports are required.

Version 1
    Share:|

    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 all versions



    PROBLEM:

     

    In the IOAGATE sysout you can see there are 3 ports (2369, 2370 & 2371) used for communication

      

    +++

      

    ECAT0TI IOAGATE(IOAGATE) RUNNING ON HOST(MVS1, 11.222.33.4)
    ECAT00I CHANNEL(MC03.TCP) TASK(004.P) LISTENING ON PORT(2369), IP(*), APPLICATION(C) 
    ECAT00I CHANNEL(DC01.TCP) TASK(003.R) LISTENING ON PORT(2371), IP(*), APPLICATION(M) 
    ECAT00I CHANNEL(DC01.TCP) TASK(002.S) LISTENING ON PORT(2370), IP(*), APPLICATION(M) 
    ECAT02I CHANNEL(MC03.TCP) TASK(005.C) ESTABLISHED CONNECTION WITH HOST(11.222.33.33), APPLICATION(C) 
    ECAT03I CHANNEL(MC03.TCP) TASK(005.C) TERMINATED CONNECTION WITH HOST(11.222.33.44)

      

    +++

      

     

      

    Because port 2371 was not opened on the firewall, the connection was terminate when trying to established a connection on the EM Server (11.222.33.44)

      

     

      

     

     


    CAUSE:

    Firewall


    SOLUTION:

     

    Legacy ID:KA409896

      

    The communication between Enterprise Manager & Control-M for z/OS is based on 3 ports:

    1. CA port (default 2369)

    2,3 GAateway - IOAGate     2 ports, default is 2370 and 2371 ( the port defined in the CCM and the next one (+1))

    Therefore, if there is a firewall between CM and Control-M for z/OS these 3 ports needs to be open

    Below is some explanation about the ports required in Control-M (Distributed Systems).

    1) "EM Gateway Port" , the default is 2370.
    CONTROL-M/Server listens on this port for a connection from CTM/EM Gateway.
    When it establishes such a connection CONTROL-M/Server will open a second connection back to CTM/EM Gateway. It will use "EM Gateway Port"+1 as the listen port for this second connection. (i.e. in a default scenario it will use 2371.)

    From a TCP/IP point of view, the CONTROL-M/Server Communication process (process name on OS level is p_ctmco for UNIX and ctmsco.exe for Windows) will listen on two ports which by default are 2370 and 2371.

     These ports should be open for incoming traffic to CONTROL-M/Server and allow bi-direction communication on these sessions


    << The same theory applies when you use Mainframe z/OS>>>



    2) "Configuration Agent Port". Default is 2369. This is a new port used only from CONTROL-M/Server v6.3.01. This port is used for actions that you perform from the Control-M Configuration Manager GUI to be sent to CONTROL-M/Server.
    This ports should be open for incoming traffic to CONTROL-M/Server and allow bi-direction communication on the session.





    On ZOS, CTMAS is using 2370

    Below is a extract taken from ctmas joblog

     20.27.11 ECAG0EI  027     *---------------------------------------------
     20.27.11 ECAG0EI  028     *        Communication Channels declarations
     20.27.11 ECAG0EI  029     *---------------------------------------------
     20.27.11 ECAG0EI  030 001 CHANNEL  ID=01,
     20.27.11 ECAG0EI  031              MODEL=DC,
     20.27.11 ECAG0EI  032              PROTOCOL=TCP,
     20.27.11 ECAG0EI  033              PORT=2370,
     20.27.11 ECAG0EI  034              SSL=NO,
     20.27.11 ECAG0EI  035              CHANNEL=ENABLE
     20.27.11 ECAG0EI  036     *
     20.27.11 ECAG0EI  037 002 CHANNEL  ID=03,
     20.27.11 ECAG0EI  038              MODEL=MC,
     20.27.11 ECAG0EI  039              PROTOCOL=TCP,
     20.27.11 ECAG0EI  040              PORT=2369,
     20.27.11 ECAG0EI  041              SSL=NO,
     20.27.11 ECAG0EI  042              CHANNEL=ENABLE
     20.27.11 ECAG0EI  043     *
     20.27.11 ECAG0EI  044     *------------------------------------------
     20.27.11 ECAG0EI  045     *        Applications Server declarations
     20.27.11 ECAG0EI  046     *------------------------------------------
     20.27.11 ECAG0EI  047 001 APSERVER APPL=(M),
     20.27.11 ECAG0EI  048              CHANID=01,
     20.27.11 ECAG0EI  049              PROCNAME=CTMAS,
     20.27.11 ECAG0EI  050              SERVER=ENABLE
     20.27.11 ECAG0EI  051     *
     20.27.11 ECAG0EI  052 002 APSERVER APPL=(C),
     20.27.11 ECAG0EI  053              CHANID=03,
     20.27.11 ECAG0EI  054              PROCNAME=CTMCAS,
     20.27.11 ECAG0EI  055              SERVER=ENABLE
     20.27.11 ECAG0EI  056     *
     20.27.11 ECAG0EI  END OF CONFIGURAION FILE
     20.27.11 ECAG0EI  043     *



    NOTES:
    1) The CTMAS is a DC (dual-channel)
    MODEL=DC --> 2 ports
    APSERVER APPL=(M) is associated with channel 01 This means the CTMAS will be sending on the defined port 2370 and be receiving on the next port 2371
       

    2) The CTMCAS is MC multichannel
    MODEL=MC --> 1 port
    APSERVER APPL=(C) is associated with channel 03 This means the CTMCAS will use the port 2369 only

     


    Article Number:

    000095519


    Article Type:

    Solutions to a Product Problem



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