Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
IRRI026I z/OS Security Server RACF Messages and Codes SA23-2291-00 |
|
IRRI026I RRSF CONNECTION {TO | FROM} system-identifier HAS
BEEN REJECTED BECAUSE RACF COULD
NOT VERIFY AT-TLS POLICY. THE service-name SERVICE COMPLETED
WITH RETURN CODE rc. ExplanationRACF® remote sharing requires its connections to be covered by an AT-TLS rule. It is AT-TLS that provides the authentication of RRSF nodes to one another, and encryption of traffic across the network. While attempting to verify the AT-TLS policy for this connection, RACF encountered return code rc on the service-name service. The value for direction can be TO, when the message is issued by the system that initiated the connection, or FROM, when the message is issued by the system that received the connection request. When the value of direction is TO, system-identifier is expressed as NODE node-name, followed by SYSNAME system-name if the target is a multisystem node. When the value of direction
is FROM, the communication failed before RRSF identified the
peer RRSF node and system name, or determined if the peer is a valid
RRSF node. Therefore, system-identifier is expressed as PEER,
followed by an IP address and a port number, separated by a colon.
If necessary, you can use the z/OS® UNIX host command to map
the IP address to a host name. See z/OS Communications Server: IP System Administrator's Commands for
more information about the z/OS UNIX host command. For example,
if the peer information displayed is 1.2.3.4:1026, issue the following
command:
System actionThe connection is rejected. The RRSF connection is placed in the OPERATIVE-PENDING-VERIFICATION state. System programmer responseAfter the condition is fixed, try the connection again with the TARGET OPERATIVE command for the failed node and system. Routing code2 and 9 Descriptor code4 RACF Security Administrator ResponseSee ../com.ibm.zos.v2r1.bpxa800/bpx1mc00.htm for more information about return codes (errnos). Try to determine the cause and fix it. If you are unable to determine the cause, contact IBM® service. |
Copyright IBM Corporation 1990, 2014
|