CONNTYPE
statements: | GROUP, PU |
dependencies: | APPN only; NODETYPE start option |
Specifies for a type 2.1 PU whether the connection is to be established as a LEN connection or attempted as an APPN connection.
If you do not code the NODETYPE start option, the CONNTYPE
operand is ignored and the connection will be a LEN connection.
- CONNTYPE=APPN
- Specifies that this connection can support parallel TGs, CP-CP sessions, and CP name change support. CONNTYPE=APPN must be coded for CPCP=YES to be valid.
- CONNTYPE=LEN
- Specifies that this connection does not support parallel TGs,
CP-CP sessions, or CP name change support. Note: For LEN sessions between PUs when CONNTYPE=APPN is coded on each PU, the CPNAME of each PU must be unique. When CONNTYPE=LEN, the CPNAMEs can be the same.
Because CONNTYPE=LEN indicates that the PU is not APPN-capable, do not code any APPN-only operands on the same PU statement. If an APPN-only operand is coded with CONNTYPE=LEN, VTAM® will issue a message warning of a parameter conflict.
Although you need to code CONNTYPE=APPN for a PU to be an APPN resource, this does not necessarily mean the PU will be APPN; a PU's characteristics are determined at activation. However, coding CONNTYPE=LEN means that the PU can only be a LEN resource, even if, at activation, the XID indicates the PU can be an APPN resource.