IRRR119I

Explanation
An attempt was made to propagate an application
update, or to return output from an application update to a downlevel
remote node.
If type is REQUEST, the application
update could not be sent to the remote partner node indicated by the
RRSFDATA profiles.
If type is OUTPUT, the
output produced by an application update could not be sent to the
remote partner node specified by the SET command. On the last handshake
with this node, the level of RACF® was
not high enough to accept application update requests or output. The
level must at least correspond to FMID HRF2230, which is available
with the OS/390 Release
3 Security Server. If SYSNAME information is present for the node
name in this message, the node that precedes the SYSNAME is a multisystem
node.

System action
If type is REQUEST, the RACF database is changed on the
source node, but the request is not sent to the target node.
If type is
OUTPUT, the output produced by an application update attempted on
this node is not sent to the node specified by the SET command. The
application update may or may not have been successfully made on this
node. Additional requests and output directed to this remote partner
node are discarded without any additional error messages.
If
handshaking occurs again between these nodes, another error message
is issued if the remote node is still at a lower level and has requests
or output being directed to it.

System programmer response
If type is REQUEST,
you should change the RRSFDATA profiles to prevent automatic direction
of application updates to this remote node until it has been updated
to a level of RACF that supports
these requests. For additional information about RRSFDATA profiles,
see z/OS Security Server RACF Security Administrator's Guide.
If type is
OUTPUT, use the SET command to prevent additional output from being
sent to this remote node. For additional information about the SET
command, see ../com.ibm.zos.v2r1.icha400/ich2a410.htm.
After
the remote system is updated, you must reestablish the connection
with it by issuing a RESTART or TARGET command to pick up the new
level.

Routing code
2 and 9

Descriptor code
6