IBM GC28-1920-01 manual prefixTARGET NODEMIAMI2 SYSNAMESYSTEM2 LOCAL OPERATIVE, On MIAMI2

Page 86

2. Issue

TARGET

DORMANT

commands

from

the

operator's

console

to

make

all

 

RRSF

conversations

dormant:

 

 

 

 

 

 

 

 

 

 

 

prefixTARGET NODE(MIAMI1) DORMANT

 

 

 

 

 

 

 

 

 

 

 

prefixTARGET NODE(ORLANDO) DORMANT

 

 

 

 

 

 

 

 

 

 

 

3. Issue

a

TARGET

command

from

the

operator's

console

to

make

MIAMI1

th

main

system

on

the

new

multisystem

node MIAMI1. The old node name is

used

for

the new

multisystem node because

the

existing

RRSFDATA

prof

on node ORLANDO already use this

node name for all automatic command

direction, automatic password direction, and

RACLINK

PWSYNC

updates.

 

prefixTARGET NODE(MIAMI1) SYSNAME(SYSTEM1) LOCAL MAIN OPERATIVE￿

 

 

 

 

 

 

Update

the

corresponding command

in

the RACF

parameter

library,

addi

MAIN and SYSNAME keywords, so that

the

updated command will

be

 

 

executed

if

the

address

space

is

recycled

or

the

system is

re

4.Issue a TARGET command from the operator's console to make MIAMI2 a non-main system on the new multisystem node MIAMI1.

prefixTARGET NODE(MIAMI2) SYSNAME(SYSTEM2) LOCAL OPERATIVE

Add the

corresponding

command

to the RACF parameter library, adding

SYSNAME

keyword, so that

the

command will be executed if the addres

space

is

recycled or

the

system is re-IPLed.

On MIAMI2:

1.To ensure that RACF activity is stopped, take down TSO/E and JES. Thi action prevents MIAMI2 from updating the RACF database without sendin updates to ORLANDO's RACF database.

2. Issue

TARGET

DORMANT

commands

from

the

operator's

console to

 

make all

RRSF

connections

dormant:

 

 

 

 

 

 

 

 

 

prefixTARGET NODE(MIAMI2) DORMANT

 

 

 

 

 

 

 

 

 

prefixTARGET NODE(ORLANDO) DORMANT

 

 

 

 

 

 

 

 

 

3. Issue

TARGET

DELETE

commands from the

operator's

console

to

delete

all

RRSF

connections:

 

 

 

 

 

 

 

 

 

 

prefixTARGET NODE(ORLANDO) DELETE

 

 

 

 

 

 

 

 

 

prefixTARGET NODE(MIAMI2) DELETE

 

 

 

 

 

 

 

 

 

Update

the RACF parameter library to delete

the

existing

TARGET

com

for

RRSF

connections.

 

 

 

 

 

 

 

 

 

Another way you can do this step is to first make

the

updates

to

parameter library,

then stop

and

restart the

RACF

address

space:

 

prefixSTOP

START subsystem-name,SUB=MSTR

4.Issue a TARGET command from the operator's console to define MIAMI2 member system of the new multisystem node MIAMI1:

prefixTARGET NODE(MIAMI1) SYSNAME(SYSTEM2) LOCAL OPERATIVE PREFIX(...) PROTOCOL(...) WORKSPACE(...)

The system that was originally single-system RRSF node MIAMI2 is now system SYSTEM2 of multisystem node MIAMI1. Remember that this system name, SYSTEM2, must match the CVTSNAME for the system. Also add this command to the RACF parameter library for SYSTEM2.

62 OS/390 V1R2.0 Security Server (RACF) Planning: Installation and Migration

Image 86
Contents Place graphic in this area. Outline is keyline only. DO NOT PRINT Security Server RACF Planning Installation and MigrationOS/390 Page Security Server RACF Planning Installation and Migration Second Edition, September 1996. AllPage Page Contents MigrationAuditing Considerations Administration ConsiderationsCustomization Considerations Chapter Operational ConsiderationsIndex 10. ApplicationPage Figures Page Notices Trademarks Who Should Use This Book How to Use ThisAbout This Book xiiiŸ The OS/390 Security Server RACF Information , PackageSK2T-2180 Where to Find More InformationSoftcopy Publications ServerUsing the Administration, H3927Elements of Security RACF Installation - Student GG24-3971Notes Ÿ Tutorial Options for Tuning GG22RACFInternet Sources Other Sources of InformationIBM Discussion Areas listserv@uga.cc.uga.eduPublications To Request Copies ofFeatures OS/390xviii OSA/SF ServiceŸ OpenEditionProduct V2R5TSO/EPage Summary of Changes Page Migration Migration Planning ConsiderationsChapter 1. Planning Customization Considerations Installation ConsiderationsAdministration Considerations Application Development Considerations Auditing ConsiderationsOperational Considerations General User ConsiderationsPage Chapter 2. Release Overview New and Enhanced Supportfunction OS/390 OpenEdition DCEidentifies introduced in OS/390 ReleaseConcepts CheckOS/390 OpenEdition Authorizing and Auditing Server Access to the CCS and WLM ServicesAuditing the Passing of Access Rights SOMobjects for MVSnon-main Multisystem NodesRRSF Network systemsTARGET OS/390 Enable and Disable FunctionsYear classes NetView1.10 Facilityidentifies function Function Not Upgradedupdated for that3. Summary of Components forRelease Class Descriptor Table CDTwhich Commandslists classes thereCommand Chapter 3. Summary of Changes to RACF Components for OS/390 15Releaselists changed Data AreasExits general-use programming interface GUPI data areFigure 12 lists changes MacrosMessages RACF macrosMessages New MessagesChanged Messages RACF Database Split/Merge Utility IRRUT400Routines PanelsPublications Library Figure 13 lists RACF panels that areFigure 16 identifies changes to RACF members of SYS1.SAMPLIB SYS1.SAMPLIBTemplates RACROUTE REQUEST=EXTRACTTemplate UtilitiesFigure 18 lists changes to RACF utilities for OS/390 Release Utility 0280Chapter 4. Planning Considerations OS/390 Security Server RACF Planning Installation and forMigrationRACF Planning Installation and Migrationfor RACF Migration StrategySoftware Requirements RACF Planning Installation and Migrationfor RACF 2.1, andHardware Requirements RACF Migration and Planning for RACFRequirements CompatibilityCompatibility Considerations for Remote Sharing Page Considerations Chapter 5. Installation ConsiderationsEnabling RACF Networksare in your existing workspace data sets when you installationconfigured install multisystem RChapter 5. Installation Considerations29 mustsysname prefixnodename local-luprefix.local-node.local-node .INMSG This section discusses storage considerations for RACF RACF Storage ConsiderationsVirtual Storage Figure 21 estimates RACF virtual storage usage, for planning purposesCustomer Additions to the CDT Subpoolinformation, OS/390see Security Server Templates for RACF onOS/390 Release Systemand IRRSXT00 Chapter 6. Customization ConsiderationsExit Processing Effects of OS/390 OpenEdition DCEIRRSXT00 Installation Exit RACROUTE REQUEST=DEFINE Preprocessing Exit ICHRDX01Cross-Linking Between RACF Users Chapter 7. Administration ConsiderationsServer RACF Security Administrators. Guide signonActivating DCEUUIDS ClassSignon to the DCE Encryption Key single signon restrictionsOpenEditionsee DCE Administration .GuideOS/390 OpenEdition DCE Application Considerations Threads and OpenEdition Planning, and inOS/390 OpenEdition Programming AssemblerLibrary Reference callable servicepthread orsecuritynp Changes to RACF Authorization ProcessingRestrictions Enhancements to the Rdceruid Callable ServiceUtility Chapter 7. Administration Considerations43 SYSMVIEWPage Auditors Guide and OS/390 Chapter 8. Auditing ConsiderationsSMF Records Server RACF MacrosInterfaces ServicesAuditing New OS/390 Report Writer Auditing OS/390 OpenEdition DCE SupportAuditing SystemView for MVS Support SMF Data Unload UtilityPage Chapter 9. Operational Considerations CommandOS/390 Security Server RACF Command Language Referencefor more Enabling and DisablingPage Servers Chapter 10. Application Development Considerations2000 Support 01yydddFNew Application Services and Security pthread the securitynpChanges to the Class Descriptor Table ServiceNew Application Authorization Programming InterfacesŸ “Macros” on page Ÿ “Templates” on page Ÿ “Utilities” on page Ÿ “Routines” on pageOpenEdition Chapter 11. General UserConsiderations Reference forPage OW08457 Chapter 12. NJE ConsiderationsAPAR OW14451 After Applying the PTFUACC Actions RequiredOW08457 NODESFAILSAFE APAR OW15408GROUP Page Nodes Chapter 13. ScenariosMigrating an Existing RRSFprefixTARGET NODEORLANDO DELETE prefixTARGET NODEMIAMI2 SYSNAMESYSTEM2 LOCAL OPERATIVEOn MIAMI2 prefixTARGET NODEMIAMI2 DELETEDELETE RACF DiagnosisOn ORLANDO prefixTARGET NODEORLANDO OPERATIVE PREFIX... PROTOCOL... WORKSPACE Note Thedirection Glossaryaccess Page programming Seegeneral-use programmingSeeinventory Seelogical Seemultisystemlogical other.single-system supervisorytask segment andDFP Index A classes continuedcontinued Page KEYSMSTR SERVERSFSCMD utilitiescontinued Page Edition OS/390 Security Server RACF Information IBM Now you can! TheIBM Online Library Productivity Page Page Communicating Your Comments to IBM commentsPublication No. GC28-1920-01 Readers Comments - Wed Like to Hear from YouOS/390 Security Server RACF Planning Installation and Migration Note CopiesBUSINESS MAILREPLY IBMPage GC28-192ð-ð1 IBMDrop in Back Cover Image Here