DISCOVER: How to configure a second IP stack for Merlon Discover

DISCOVER: How to configure a second IP stack for Merlon Discover

The steps below can be used to change the Discover LSNINI and RD Macro files.

1. Add an additional section to the LSNINI file in the Discover installation subvolume for
    each TCP/IP stack to identify the TCP/IP connection in question.

    Example:  (new entries in red):
    
    [TCPIP]
    Process=$ZB1BB
    Port=7135
    ListenIPAddr=192.168.63.25
    [LISTEN]
    Program=DSC
    AppPrefix=DCV
    CPUS=0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15
    Priority=150
    MaxServers=32

    [ANOTHERTCPIP]
    Process=$ZB1AC
    Port=8235
    ListenIPAddr=<ip address>  (where <ip address> is a valid ip address on which to listen for a connection request, e.g. 192.168.10.22)

   This defines two TCP/IP connections, one on TCP/IP process, $ZB1BB, port 7135 and
   another on $ZB1AC, port 8235.

2.  The RD macro that starts Discover will need to be updated to start a listeners the
     connection added in step 1:


     ?TACL MACRO
     DELETE DEFINE =PTCPIP^FILTER^KEY
     ADD DEFINE =PTCPIP^FILTER^KEY, CLASS MAP, FILE MSC
     [#IF [#EMPTY [#PROCESSINFO/PIN/$KL340]] |THEN|
        DELETE DEFINE =TCPIP^PROCESS^NAME
        ADD DEFINE =TCPIP^PROCESS^NAME,CLASS MAP,FILE $ZB1BB
        PARAM TCPIP^PROCESS^NAME $ZB1BB

        [#IF [#PROCESSEXISTS $ZHOME] |THEN|
           RUN $D1.KWDC340.LISTEN/NAME $KL340, IN $ZHOME, OUT $ZHOME, TERM
               $ZHOME, NOWAIT/
        |ELSE|
           RUN $D1.KWDC340.LISTEN/NAME $KL340, NOWAIT/
        ]

         [#IF [#PROCESSEXISTS $ZHOME] |THEN|
            RUN $D1.KWDC340.LISTEN/NAME $KL341, IN $ZHOME, OUT $ZHOME,
                TERM $ZHOME, NOWAIT/ --TCPSECTION ANOTHERTCPIP
         |ELSE|
            RUN $D1.KWDC340.LISTEN/NAME $KL341, NOWAIT/ --TCPSECTION
                ANOTHERTCPIP
         ]
      ]

      [#IF [#EMPTY [#PROCESSINFO/PIN/$KD340]] |THEN|
         [#IF [#PROCESSEXISTS $ZHOME] |THEN|
            RUN $D1.KWDC340.DISCOVER/OUT $ZHOME, TERM $ZHOME, CPU 0, NAME
                $KD340, PRI 100, NOWAIT/
         |ELSE|
            RUN $D1.KWDC340.DISCOVER/OUT $ZHOME, term $ZHOME, CPU 0, NAME
                $KD340, PRI 100, NOWAIT/
         ]
      ]

This example will start two listener processes.  The first, $KL340, will use the default TCP/IP connection defined in LSNINI as [TCPIP] and the second, $KL341, will use the entry for [ANOTHERTCPIP].





If this article did not provide a solution, please open a case with our support team by sending an email message to support@xypro.com.


    • Related Articles

    • Discover: How to migrate Discover

      If you wish to move your Discover environment to a different location while maintaining configuration and history, perform the following steps: 1. Shut down Discover. This can be done from the client Tools menu or via the DCI> EXIT SHUTDOWN command ...

    • Where can older copies of Merlon products be found?

      Older copies of the Merlon (non-shipping version) products can be found internally on the XYPRO file server at the following locations: Discover \\fs.xypro.com\filesrv\Merlon_Files\Discover MARS \\fs.xypro.com\filesrv\Merlon_Files\MARS SQLXPress: ...

    • Discover - Items to gather when troubleshooting Discover Issues

      Items to ask for from the customer when troubleshooting Discover issues. The Discover version, both Server and Client versions Server - VPROC of the Discover object Client - Help/About EMS messages covering the time period of the scan at issue Any ...

    • XAC: How to configure XAC TACLs for static SSH windows

      Add a static service via the SSH STNCOM utility Example: STNCOM $<process name> (Where $<process name> is the name of a valid STN process, e.g. $ZPTY ADD SERVICE AUDTACL, TYPE STATIC 2. The service added in step #1 will need several static windows ...

    • XYPRO GUIs can't connect to the NonStop host after the host ip address is changed

      If the user cannot connect to the NonStop host after the host ip address has been changed, then both XYGATETR (XTR) on the NonStop host and the GUI must be modified to reflect the new ip address 1. If XYGATE/TR (XTR) is configured on multiple NonStop ...