Hi Radoslaw,

It is fine to copy an off line RACF database using the tools you named. For a 
live RACF database, however, by not using IRRUT200, you risk copying the 
database while RACF is in the midst of updating it, in which case the copy may 
have integrity errors. A copy of a live database made using some other tool 
will be fine as long as no updates were being made at that particular point in 
time. IRRUT200 is much safer because it ensures no updates are in progress when 
making its copy. I wouldn't recommend using anything other than IRRUT200 
(preferably) or IRRUT400 for making backups or copies of a live RACF database.

Regards, Bob

Robert S. Hansel
Lead RACF Specialist
RSH Consulting, Inc.
617-969-8211
www.linkedin.com/in/roberthansel
http://twitter.com/RSH_RACF
www.rshconsulting.com

-----Original Message-----
Date:    Tue, 16 Feb 2016 21:48:37 +0100
From:    "R.S." <[email protected]>
Subject: Re: [Bulk] Re: [Bulk] UADS (was Re: [Bulk] Re: COBOL v5)

W dniu 2016-02-15 o 12:48, Robert S. Hansel (RSH) pisze:
> I wholeheartedly agree with Joel's recommendation for having a backup copy of 
> the RACF database readily available for recovery. I just want to add that it 
> is crucial to use RACF utilities to create the backup and to allocate it with 
> the proper characteristics. The preferred utility to use to create the backup 
> is IRRUT200 which momentarily serializes the database, thereby preventing 
> updates, while it copies the database. IRRUT400 can also be used, but it 
> locks the database which you then have to unlock. The backup should be 
> allocated as one extent, contiguous, and non-movable and, if using IRRUT200, 
> with the exact same size as the source.

While I still support to use UT200 to perform copy of RACF db, I have to 
admit I did many tests in the past when I intentionally used RACF db 
done by ICEGENER, IEBGENER or ADRDSSU DUMP. With no "luck", that mean I 
never got inconsistent result. At least none of RACF utilities detected 
the inconsistency. In other words even such copy was usable.
Of course I still recommend to use proper tool for that.

BTW: all my tests were done against monoplex configurations.
BTW2: the tests had some reason behind, it wasn't just "hey, let's put 
egg to microwave owen and see". ;-)


-- 
Radoslaw Skorupka
Lodz, Poland

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

Reply via email to