Chapter 4. Converting APPC connections to TCP connections 103
location 4. Setting up the new protocol at location 2 and making it operative at 4 works fine on
system ADCD. It fails both new commands, but SC80 and SC81 fail in a subtle way:
The target operative command at location 3 fails because it does not specify a protocol,
and PLEX76 has both APPC and TCP defined.
Because command 3 failed, the APPC definition of PLEX76 is still in the initial state. You
cannot make the new TCP protocol operative unless the old protocol is at least dormant.
For more information, see 4.9, “Order of protocol definition” on page 92.
You can try to fix this adding dormant to the initial definition of the APPC protocol for PLEX76
at position 5 in Figure 4-21 on page 102. However, that fix will not work because at that point,
the local node is not dormant or operative, so dormant for a remote node is not yet allowed.
The easiest way to fix this problem is to add protocol(appc) to command 3 (Figure 4-22).
Figure 4-22 Merging the TCP definition for PLEX76 into the IRROPTxx file on PLEX81
Although the placement of the TCP definition for PLEX76 is consistent with the structure of
the IRROPTxx file, it took a few tries to get it correct. For example, an attempt was made to
add dormant to location 5, with the expectation that it would work, only to have it fail. There
were a few deletion and redefinition cycles of the nodes on the test system before the
changes were made properly. This aspect conflicts with the original intent of allowing protocol
conversion to happen on live systems with no downtime.
The safest (most likely to work the first time) place to add the TCP definition for PLEX76 is at
location 4 in Figure 4-21 on page 102. This location is after the APPC protocol is made
operative. The old protocol is fully set up and operative. Because all of the new commands
specify protocol(tcp), they are ignored by z/OS V1R11 system ADCD. This simplicity and
reduced need to test comes at a cost of a less organized IRROPTxx file.
4.14.3 Execution of shared IRROPTxx file on current and earlier systems
Either way, when IRROPTxx is run on sc80 and sc81, there is a brief protocol conversion from
APPC to TCP each time. Because the APPC definition to SC80 and SC81 does not exist in
IRROPTxx on PLEX76, the APPC connection fails each time (Example 4-17).
Example 4-17 Excerpts from the output of set include(xx) on system SC81
#SET INCLUDE(XX)
...
TARGET NODE(PLEX81) SYSNAME(SC81) MAIN LOCAL PREFIX(SYS1.RACF) -
WORKSPACE(VOLUME(BH8ST4)) PROTOCOL(APPC(LUNAME(RRSFSC81)))
...
TARGET NODE(PLEX75) SYSNAME(SC74) PREFIX(SYS1.RACF) -
WORKSPACE(VOLUME(BH5ST2)) PROTOCOL(APPC(LUNAME(RRSFSC74)))
TARGET NODE(PLEX76) PREFIX(SYS1.RACF) -
WORKSPACE(VOLUME(BH6ST1)) PROTOCOL(APPC(LUNAME(RRSFSC76)))
TARGET NODE(PLEX76) PROTOCOL(TCP(ADDRESS(9.12.4.126))) -
PREFIX(RRSF.RACF) WORKSPACE(VOLUME(BH5ST2))
TARGET NODE(PLEX81) SYSNAME(SC81) OPERATIVE
...
TARGET NODE(PLEX76) PROTOCOL(APPC) OPERATIVE
TARGET NODE(PLEX76) PROTOCOL(TCP) OPERATIVE
SET INCLUDE(TP)

Get RACF Remote Sharing Facility over TCP/IP now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.