Migrating APPC and MRO connections to IPIC
You can migrate your existing MRO, APPC, and LUTYPE6.1 connections to IPIC connections. Existing connections continue to operate as before. The IPCONN definition takes precedence over the CONNECTION definition; that is, if an IPCONN and a CONNECTION have the same name, CICS® uses the IPCONN definition.
Before you begin
About this task
Procedure
Example
This example of an APPLID table shows the format that
you must use. The table following the example has reference information
for the table format.
Table column | Length | Description |
---|---|---|
APPLID | char 8 | Unique identifier or .DEFAULT. The APPLID must match the NETNAME of the associated CONNECTION definition. See Equivalent attributes on IPCONN definitions. Use .DEFAULT to specify default values for NETID or TCPIPSERVICE. The leading dot prevents the word DEFAULT being used as a valid APPLID. Only one .DEFAULT row is allowed in the table. |
Separator | char 1 | Any alphanumeric character. |
NETID | char 8 | Network identifier. When left blank, the default NETID specified by the .DEFAULT row is used. |
Separator | char 1 | Any alphanumeric character. |
PORT | char 5 | Listening port number |
Separator | char 1 | Any alphanumeric character |
HOST | char 55 | TCP/IP host name |
Continuation column | char 1 | Normally blank. Any nonblank character in this field indicates that the host name is longer than 55 characters and continues in the HOST column in the following row. |
You can use this example JCL to invoke DFH0IPCC through
DFHCSDUP.