Bo, I suggest ctc, not 3172. As we note in the Redbook, most customers now run OSAs in QDIO mode, not LCS (3172) mode, and unless the customer really uses LCS mode in the real world, which is pretty rare, we don't suggest this. I will also remind you that we support TCP/IP CTC, not SNA CTC. So hopefully your customer is setting up for TCP/IP connectivity over CTCs, and not SNA. I would also add 3172 (OSA in non-QDIO mode) is not supported for SNA by zPDT either; only TCP/IP. If the connectivity is for things other than TCP/IP and SNA, it is out of my area of expertise.
The Redbook does a pretty good job in showing the devmap requirements for defining an awsctc stanza in chapter 16 that you alluded to above. I would love to test this, but I am leaving on vacation, and thought I would give you a few thoughts before I go. Hopefully, if I am wrong, someone else will chime in.
If this connectivity is indeed for TCP/IP, in addition to the device map, you have to define a CTC Device and Link in TCP/IP. The device number in the CTC Device statement must match the device address for the CTC in the devmap. In the real world, you only define one address in TCP/IP, but you really use 2 consecutive addresses, one for read and one for write. What I am not sure of is if you have to define 2 devices in the devmap for TCP/IP to use it, or if zPDT "does this for you." My guess is you do have to define two, they need to be consecutive, and they must use different ports on the devmap. But don't quote me on any of that. I will try this when I return.
Hope that gives you a start.
Bebe
RDTBebe