Jump to navigation Jump to search
M204.2911 Attempted connect from processgroup token to IPV6 server token2, but link token3 is IPV4
The link named in the message is defined as using TCP IPV4 addressing, but the processgroup is attempting to connect to a remote server using IPV6 addressing. This will usually fail with TCP/IP socket error code 121 (EINVAL).
The link will be IPV4 if one of these is true:
- The local ID is a symbolic name that has no IPV6 address.
- The host machine is not configured for IPV6 addressing.
LOOKUP=IPV4ONLYwas specified on the DEFINE LINK command.
The processgroup will attempt to connect to a remote IPV6 server if one of these is true:
- Its remote ID resolves to an IPV6 address, and
LOOKUP=IPV4ONLYwas not specified on the DEFINE PROCESSGROUP command.
- Its remote ID is an explicit, colon-separated, IPV6 address.
|RETCODEO=0||Sets online return code|
|RETCODEB=4||Sets batch (single user) return code|
|CLASS=E||Error class; the message can be suppressed with the X'04' bit setting of the MSGCTL parameter|
|AUDITMS||Writes the message with line type MS to the audit trail|
|NOCOUNT||Does not increment the error count (ERCNT) parameter|