One of the customers need to setup MQ on zD&T and wanted to configure a static ip with zOS so opted scenario 4 for the network settings. Even after trying multiple changes in Devmaps and zOS settings scenario 4 is not working. Currently the system is working with scenario 2 and scenario 5 which helped the customer to transfer the whole files from host to zD&T thruogh FTP.

 

Need you suggestion to configure network setting to support MQ on zD&T.

 

 

Hi Jose, you will need to follow some steps: 

1. your customer needs to have a fixed and dedicated IP. Ask them to talk to their network administrator for that. ON my sample below I am using 9.26.158.211. 

2. Change the devmap config file on awsosa stanzas to look like that: 

  [manager]  # tap0 define network adapter (OSA) for communication with Linux
  name awsosa 0009 --path=A0 --pathtype=OSD --tunnel_intf=y   # QDIO mode
  device 400 osa osa --unitadd=0
  device 401 osa osa --unitadd=1
  device 402 osa osa --unitadd=2

  [manager]  # eno1 define network adapter (OSA) for communication with network
  name awsosa 0019 --path=F0 --pathtype=OSD                   # QDIO mode
  device 404 osa osa --unitadd=0
  device 405 osa osa --unitadd=1
  device 406 osa osa --unitadd=2

3. On the z/OS TCPIP config file: change DEVICE, LINK, HOME and BEGINRoutes as follows: 

DEVICE PORTA         MPCIPA                                                     

LINK   TAP0          IPAQENET  PORTA                                           

HOME   10.1.1.2      TAP0                    çtunneling address to Linux router                                    

                                                                               

DEVICE PORTB         MPCIPA                                                    

LINK   ETH1          IPAQENET  PORTB                                           

HOME   9.26.158.211  ETH1                                                      

;                                                                              

BEGINRoutes                                                                    

ROUTE 10.0.0.0        255.0.0.0       =         TAP0  MTU 1492                 

ROUTE 9.26.158.0      255.255.254.0   =         ETH1  MTU 1492                 

ROUTE DEFAULT         9.26.158.1      ETH1  MTU 1492                           

ENDRoutes                                                                   

4. In the end of this PROFILE member, put both starts as follows: 

    START PORTA    
    START PORTB   

5. Check if their ATCCON00 VTAM member points to the correct OSATRLx member. The one ready to do it in ADCD config is OSATRL2. You will find it in ADCD.Z*.VTAMLST dataset. 

6. If all is correct, after IPL all address 400,401,402 and 404,405,406 will be allocated to VTAM address space. Issue this command in the console to check it: 

    D U,,,400,8 

IEE457I 08.52.28 UNIT STATUS 866                    
UNIT TYPE STATUS        VOLSER     VOLSTATE      SS 
0400 OSA  A-BSY                                   0 
0401 OSA  A                                       0 
0402 OSA  A-BSY                                   0 

0403 OSA  OFFLINE 

0404 OSA  A-BSY                                   0 
0405 OSA  A                                       0 
0406 OSA  A-BSY                                   0 

0407 OSA  OFFLINE  

 

Those above steps should be enough.