got ya thanks..

was hoping the setup from BPX.DEFAULT.USER to the new one would be 
painless..picked up the following and assume this is best steps to take...
This sound familiar ??

http://ourdigitalmags.com/display_article.php?id=1124854




From:   Elardus Engelbrecht <[email protected]>
To:     [email protected]
Date:   10/14/2013 07:47 AM
Subject:        Re: RACF
Sent by:        IBM Mainframe Discussion List <[email protected]>



Ron Wells wrote:

>Elardus..Sorry did not get back with you...

It is all right. Never mind! :-)

>need to get with racf person...made first step...reading and slowly going 
through this on test lpar to see if we break anything..

I'm glad for your part.

>we do currently use idcams to backup the database...been in place 
since???

With IDCAMS? If you really needed to use IDCAMS, which is not recommended, 
I would like suggest that you use IRRUT200 (and also IRRUT400) at least to 
verify the integrity of the copy result, but you can use IRRUT200 to make 
a backup while ensuring a lock is hold. Then thereafter you can use 
IDCAMS, DFDSS, whatever to copy your newly created backup of RACF DB.

>we did use dfdss this time to backup and restore to different name...and 
reipl'd using that name...leaving old one alone--just incase..

This is a good method, which I also used during the Y2K fun days full of 
havoc where I have to create several dozen LPARs with their own parmlib, 
vtamlst, RACF DB, HSM, JES2, etc. All with their own naming standards...

;-)

Groete / Greetings
Elardus Engelbrecht

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
Email Disclaimer
This  E-mail  contains  confidential  information  belonging to the sender, 
which  may be legally privileged information.  This information is intended 
only  for  the use of the individual or entity addressed above.  If you are not 
 the  intended  recipient, or  an  employee  or  agent responsible for 
delivering it to the intended recipient, you are hereby notified that any 
disclosure,  copying, distribution, or the taking of any action in reliance on 
the contents of the E-mail or attached files is strictly prohibited.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to