Rick makes a good point. Once the great 1.9 divide has been crossed, we've
never found any reason not to share the RACF data base in each plex. Even
when templates had to be applied to the data base itself, lower releases
always tolerated them. I know everyone does migration differently, but we
have kept the same data base allocations and content since at least the
early 90s. RACF *data* is never migrated along with ServerPac.
Rick Fochtman
<[EMAIL PROTECTED]
T> To
Sent by: IBM [email protected]
Mainframe cc
Discussion List
<[EMAIL PROTECTED] Subject
.EDU> Re: Question regarding RACF
migration.
11/22/2007 08:24
AM
Please respond to
IBM Mainframe
Discussion List
<[EMAIL PROTECTED]
.EDU>
------------------------<snip>-----------------------
>I had a PHB presentation, but can't find it. Long story short the big
>conversion was RACF 1.8 to 1.9. After that there are incremental levels of
the
>DB added by using the extended fields in data base records. These fields
are
>examined by newer releases. So theoretically you can share DB's from 1.9
on
>with just about any level. This always scared me, so for production I
always
>copied the old databases to new and ran the template update.
>
>
-------------------------<unsnip>-----------------------
I just ran the template update and shared the databases between old and
new level.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
