DEFINE PROCESSGROUP command: Horizon for TCP/IP

From m204wiki
Revision as of 01:04, 28 February 2013 by Alex (talk | contribs) (Automatically generated page update)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Summary

Privileges
User 0 or system manager
Function
Sets up a TCP/IP connection via Horizon for processgroup. Supported in all operating systems.

Syntax

DEFINE PROCESSGROUP name [LIKE previousname] WITH SCOPE=SYSTEM LINK=linkname REMOTEID={address | symbolicaddress} LOOKUP=IPV6ONLY|IPV4ONLY|ANY INLIMIT={nnnn | 0} [PORT=nnnnn] [GUESTUSER={ACCEPT | REJECT}] [LOGIN=TRUST | NOTRUST}] [MASK={dotted-decimal | 255.255.255.255}]

Where:

  • name is used on DEFINE PROCESS commands to refer to this processgroup. The length of the name must be eight characters or less. ALL is a reserved word and cannot be used.

  • LINK is required and associates the group with a locally defined link that implies the transport type and conversation protocol. A linkname must match the name used in a local DEFINE LINK command.

  • REMOTEID=address specifies the network address of one or, if a mask is specified, many partner remote nodes in the network.

    address can be:

    • a 32-bit number written in dotted-decimal notation, such as 182.148.55.206

    • (z/OS only) an IPv6 address, with up to 8 halfwords separated by colons, such as

      C0:12:46:F0:00:00:00:01

      , which can also be written as

      C0:12:46:F0::01

      . In other words, the double colon shows that there are missing halfwords of binary zeros.

    REMOTEID=symbolicaddress specifies the symbolic address of one partner remote node in the network, such as MYMVS1, or SMTP.MYDOMAIN.COM.

    The MASK parameter cannot be used with REMOTEID=symbolicaddress.

Example

To set up a Horizon for TCP/IP connection, take the following steps. You define a link, processgroup, and a process for a client and open the link. Then you define the same items on the server side and open the link, as shown in the following steps.

For the client

  1. Define a link for a client named TCPC.

    DEFINE LINK TCPC WITH SCOPE=SYSTEM PROTOCOL=IP - LOCALID=192.207.28.129 INBUFSIZE=4096 - TRANSPORT=TCPSE - CONNECTIONS=60 SERVPORT=65535

  2. Define a processgroup named TCPG

    DEFINE PROCESSGROUP TCPG WITH SCOPE=SYSTEM LINK=TCPC - INLIMIT=30 OUTLIMIT=30 REMOTEID=192.207.28.129 - MASK=255.255.255.255 PORT=65534

    The value of PORT, 65534, is used as the SERVPORT value in the DEFINE LINK command for the server.

  3. Define a process named CPR

    DEFINE PROCESS CPR WITH SCOPE=SYSTEM - DATALEN=9999 PARTNER=SPR - DESTINATION=TCPG UIDSOURCE=OPEN

    The value of PARTNER, SPR, is the process name in the DEFINE PROCESS command for the server.

  4. Open the client link named TCPC

    OPEN LINK TCPC

For the server

  1. Define a link for the server named TCPS that corresponds to the link for the client. In this example, the SERVPORT value 65534 matches the PORT value defined in the client DEFINE PROCESSGROUP command.

    DEFINE LINK TCPS WITH SCOPE=SYSTEM PROTOCOL=IP - LOCALID=192.207.28.129 INBUFSIZE=4096 - TRANSPORT=TCPSE - CONNECTIONS=60 SERVPORT=65534

  2. Define a processgroup TSPG for the server

    DEFINE PROCESSGROUP TSPG WITH SCOPE=SYSTEM - LINK=TCPS - INLIMIT=30 OUTLIMIT=30 REMOTEID=192.207.28.129 - MASK=255.255.255.255

  3. Define a process named SPR for the server

    DEFINE PROCESS SPR WITH SCOPE=SYSTEM FROM TSPG - DATALEN=9999 TIMEOUT=0 - SUBSYSTEM=CONS SUBSYSPARM='CONSPROC RE-TPROC - NOPEN'

    The process name defined for the server must match the value of the PARTNER parameter in the client DEFINE PROCESS command.

  4. Open the server link named TCPS

    OPEN LINK TCPS

Usage notes

IPv6 addressing

IPv6 addressing is supported on IBM z/OS systems only.

Take care using symbolic addresses when your Online is running on a host that is enabled for IPv6 addressing. If your Online needs to communicate with IPv4 partner nodes, you must specify LOOKUP=IPV4ONLY on the LINK or PROCESSGROUP definition. For details, see "Usage Notes" in DEFINE LINK: Horizon for TCP/IP.