Paul:
While RTVDSKINF will give you generalized information about the IFS. The RTVDIRINF can give you very detailed information about all the mounted directory objects on the system. I say mounted since we can now have UFDS that may or may not be mounted when you run your command.
My guess is you want both commands and then you'll have a complete database (along with the DSPOBJD command) of everything that is on the system. More information than you really need, but you can cull out what you don't want with SQL easily enough.
Keep in mind that a significant amount of the IFS is logs, and similar type files that will never be the same except on a replicated system, and even then they will be different in some areas.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> On Behalf Of Steinmetz, Paul
Sent: Wednesday, December 26, 2018 9:22 AM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxx>
Subject: RE: P7 to P9 test migration/recovery using BRMS - issues/resolutions
Jim / Rob,
< Clearly a DSPOBJD *all/*all into a file on both systems the use SQL to compare libraries is an option too.
I like your idea.
At first, I was simply thinking of comparing library totals.
But a match of all objects in the libraries (and IFS), source against target, would give a fast, accurate, confirmation of the restore.
I run a RTVDSKINF daily, takes about 7 minutes, which I use for multiple other purposes.
RTVDSKINF creates QAEZDISK PF, about 2,000,000 records(objects).
From a previous post, Rob also suggested a RTVDIRINF.
RTRDIRINF takes about 3 hours to run, I only run this as needed.
RTVDIRINF creates QAEZD000#O and #D PF, about 2,500,000 records(objects).
1) Before I create this, what additional detail is RTVDIRINF reporting that RTVDSKINF is lacking?
2) Has anyone from the group ever used either of these to confirm any missing objects on the target system from a migration or a system recovery?
3) Any thoughts from the group?
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Oberholtzer
Sent: Wednesday, December 19, 2018 9:07 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: P7 to P9 test migration/recovery using BRMS - issues/resolutions
OK, starting from the top:
Always download the latest code especially for LIC from ESS and use that. And since you did not use the LIC from the tape, you really need to reapply all your PTFs. Better yet, get all new ones and get them applied. You may have done this already. Even if you think this is resolved, it might not be. I've had this bite in the past, hard. Since you can apply all new PTFS to save grief down the road.
Since you told BRMS to use multiple drives on the restore, and it did not, that's an error and a PMR should be called in. I'm glad you manually corrected the problem.
To confirm the restore was complete, I always use the *PRINT on the restores, then search for "not restored" in the spool file. Clearly a DSPOBJD *all/*all into a file on both systems the use SQL to compare libraries is an option too.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> On Behalf Of Steinmetz, Paul
Sent: Tuesday, December 18, 2018 3:02 PM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxx>
Subject: P7 to P9 test migration/recovery using BRMS - issues/resolutions
1) 5770SS1 *BASE *ERROR IBM i
CHKPRDOPT PRDID(5770SS1)
Product 5770SS1 release V7R3M0 L00 option *BASE load 2924 correctly installed.
Required PTF 5770999-MF65144 V7R3M0 not in correct status for PTF 5770SS1-SI68084 V7R3M0.
Required PTF 5770999-MF65297 V7R3M0 not in correct status for PTF 5770SS1-SI68338 V7R3M0.
PTF requisite errors found for product 5770SS1.
Resolution.
CHKPRDOPT PRDID(5770SS1) VFYREQPTF(*NO)
Resolved the issue.
5770SS1 *COMPATIBLE IBM i
Issue resolved.
2) Because LIC was installed from I_BASE_01 RS-73--F DVD that shipped with my P9, I was missing some PTFS that were temp applied on the source system are appearing as Cover Letter Only on the target.
Resolution.
slip install LIC
http://www-01.ibm.com/support/docview.wss?uid=nas8N1018561
Issue Resolved.
3) When doing an D-IPL with HMC profile set to alternate install deice, (FC tape library), and then setting the alternate IPL device during the IPL,
Unable to allocate resources - installation failed
Alternate Installation Device Failed
The alternate installation device or media failed.
Resolution
When HMC profile is set to alternate IPL device ( (FC tape library), DO NOT set the alternate install options during the IPL, simply continue.
Issue resolved.
4)All the *IBM libraries, which were being restored form a four volume system save, were experiencing significant tape seeking, unloading, loading during the recovery.
I had BRMS recovery set to use all 4 drives, I'm not sure why this is occurring.
Temp Resolution – Open item.
I only selected the restore items from the same volume which were in sequence.
Restore streamed with no rewind, etc.
I repeated this process for each volume listed in the recovery.
Issue temporarily resolved.
Waiting for answers from IBM development on how to perform the restore when the save had multiple, concurrent volumes.
5) STRRCYBRM OPTION(*SYSTEM) (report shows correct volume) is showing a duplicated volume not in the library, as opposed to the original volume which is in the library.
Found an old PMR which had us create BRMS dtaara , QUSRBRM/Q1AIGNRDUP.
I don’t remember the specifics on why we had to do this.
https://www.ibm.com/developerworks/community/wikis/home - !/wiki/IBM%20Backup%2C%20Recovery%20and%20Media%20Services%20%28BRMS%29%20for%20i/page/Include%20both%20original%20save%20media%20and%20duplicate%20save%20media%20in%20Recovery%20Volume%20Summary%20Report%20-%20Q1AIGNRDUP<
https://www.ibm.com/developerworks/community/wikis/home#!/wiki/IBM%20Backup%2C%20Recovery%20and%20Media%20Services%20%28BRMS%29%20for%20i/page/Include%20both%20original%20save%20media%20and%20duplicate%20save%20media%20in%20Recovery%20Volume%20Summary%20Report%20-%20Q1AIGNRDUP>
We also changed the command defaults for USEDUPMED from *NO to *YES.
Use duplicate media . . . . . . USEDUPMED *YES
Resolution.
Removed BRMS datara , QUSRBRM/Q1AIGNRDUP and changed command defaults for USEDUPMED from *YES to *NO.
Issue resolved.
5) STRRCYBRM OPTION(*SYSTEM) is included 3 libraries for recovery that were deleted over 6 years ago.
Resolution
Changing Show deleted libraries from default of *YES to *NO DID NOT resolve this issue.
Either expire the old tape or change the Beginning date .from *BEGIN to a date after 6/3/12.
Issue resolved.
6) STRRCYBRM OPTION(*SYSTEM) is including a 6 year old LTO5 volume, 2 sequences, (currently LTO7).
Saved Save Save Save Parallel Volume File Expire
Item Date Time Type Devices Serial Sequence Date
*NONSYS 6/03/12 12:24:59 *FILE 001060 681 *PERM
QDOC 6/03/12 12:41:40 *FILE 001060 1015 *PERM
Resolution.
Either expire the old tape or change the Beginning date .from *BEGIN to a date after 6/3/12.
Issue resolved.
7) Several thousand X-Lib LF initially not restored, later restored via deferred object.
How does one confirm that all X-LIB deferred LF got restored.
Resolution.
Confirmed by looking at WRKF FILE(QRECOVERY/QADBRSDFR) No records exist, all deferred objects were restored.
Issue resolved.
8) How does one easily determine what objects, if any, did not get restored?
Verifying whether objects are restored successfully
https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_73/rzarm/rzarmvfyrst.htm
Resolution
Open, 100% restore not confirmed.
Thank You
_____
Paul Steinmetz
IBM i Systems Administrator
Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071
610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home
psteinmetz@xxxxxxxxxx<mailto:psteinmetz@xxxxxxxxxx>
http://www.pencor.com/
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
midrange.com
