Robert,
It's IMHO very obvious that offline RACFdb can be copied as regular
dataset, Actually I did mean copy of live RACF db with the tools like
IEBGENER or ADRDSSU (in monoplex) with no ill effects. So my *very
limited* experience says it is not so easy to get inconsistent copy of
RACF db.
Of course it is still russian rulette, so even if the risk is small (I
didn't say that!), it's still worth to use proper tools.
I'd suggest always use UT200 then UT400 (against the copy) if needed.
Reason: UT200 is easier to use and faster.
Regards
--
Radoslaw Skorupka
Lodz, Poland
W dniu 2016-02-17 o 11:49, Robert S. Hansel (RSH) pisze:
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". ;-)
---
Treść tej wiadomości może zawierać informacje prawnie chronione Banku
przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie
jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem
niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania
adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie
lub inne działanie o podobnym charakterze jest prawnie zabronione i może być
karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie
zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość
włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku.
This e-mail may contain legally privileged information of the Bank and is
intended solely for business use of the addressee. This e-mail may only be
received by the addressee and may not be disclosed to any third parties. If you
are not the intended addressee of this e-mail or the employee authorized to
forward it to the addressee, be advised that any dissemination, copying,
distribution or any other similar activity is legally prohibited and may be
punishable. If you received this e-mail by mistake please advise the sender
immediately by using the reply facility in your e-mail software and delete
permanently this e-mail including any copies of it either printed or saved to
hard drive.
mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa,
www.mBank.pl, e-mail: [email protected]
Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru
Sądowego, nr rejestru przedsiębiorców KRS 0000025237, NIP: 526-021-50-88.
Według stanu na dzień 01.01.2016 r. kapitał zakładowy mBanku S.A. (w całości
wpłacony) wynosi 168.955.696 złotych.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
