the description of the TARGET commandOS/390 inSecurity Server (RACF) Command Language Referencefor details.
If any of the INMSG | or | OUTMSG | workspace | data | sets | are | not empty | ||||||||||
should rename | them | to | follow | the | new | naming | convention. For | an | example | ||||||||
JCL | to | perform | this |
| task, | see | Figure 20 | on | page 30. |
|
|
| |||||
6. Restart | the | RACF | subsystem | address | space | to | pick | up the | renamed | ||||||||
data | sets and | the | updated | code. |
|
|
|
|
|
|
|
7.Use the IRRUT400 utility to unlock the RACF database. Specify PARM='UNLOCKINPUT' with no OUTDD statements in the JCL. For more information on IRRUT400, OS/390see Security Server (RACF) System Programmer's Guide.
As long as all the RRSF nodes | in | an RRSF network are | |||
nodes, | nodes | with multisystem | node | support | installed can continue to co |
with nodes that do not have | the support | installed. However, the multi | |||
support | must | be installed on | each | RRSF node in an RRSF network before |
multisystem | node | can be defined in the network. If you attempt to | |||
multisystem | node | and | multisystem | node | support has not been installed on |
node in the network, | RACF issues | an | error message. |