× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I am opening a ticket with IBM BRMS support.
I think the issue is there is old, unexpired, BRMS media that contains the deleted libraries.
*OMITLIB with *DELETE should handle this, but is not.
Changing the dates to the last full system save does work, and is another option.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Friday, May 31, 2019 7:04 AM
To: Midrange Systems Technical Discussion
Subject: RE: STRRCYBRM *SYSTEM *RESTORE - time period for recovery recommendations

By "including" those libraries is BRMS just printing them out as items of interest, or is it actually restoring them?
Maybe you should open a ticket.
Would it help to change the dates to only go back to your last full system save?

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Steinmetz, Paul via MIDRANGE-L
Sent: Thursday, May 30, 2019 4:18 PM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
Subject: RE: STRRCYBRM *SYSTEM *RESTORE - time period for recovery recommendations

*OMITLIB set to *DELETE.
*DELETE
Exclude deleted libraries from the recovery. Please note that only
libraries deleted before the last run of Start Maintenance for BRM
(STRMNTBRM) will be omitted.

It "appears" that *DELETE is not WAD.

STRMNTBRM is run daily on all LPARS.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Thursday, May 30, 2019 3:54 PM
To: Midrange Systems Technical Discussion
Subject: RE: STRRCYBRM *SYSTEM *RESTORE - time period for recovery recommendations

Did you read the help on *OMITLIB?
If so, how often do you run STRMNTBRM?

On one of my systems:
WRKJOBSCDE BRM*
Next
-----Schedule------ Recovery Submit
Job Status Date Time Frequency Action Date
BRMMAINT SCD *ALL 06:45:00 *WEEKLY *SBMRLS 05/31/19
BRMRECOVER SCD USER DEF 06:30:00 *WEEKLY *NOSBM 05/31/19
BRMREORG SCD *MONTHSTR 00:01:00 *MONTHLY *SBMRLS 06/01/19

Command . . . . . . . . . . . : STRMNTBRM RMVMEDI(*REUSE) PRTEXPMED(*NO) PRT
VSNRPT(*NO) PRTBKUACT(*NO) PRTRCYRPT(*RCYANL *SAVEXCP)

BRMRECOVER is a custom program which creates the BRMS recovery report and stores it as a PDF on three geographically dispersed servers.
The "weekly" entries run all 5 working days.


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Steinmetz, Paul via MIDRANGE-L
Sent: Thursday, May 30, 2019 2:23 PM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
Subject: STRRCYBRM *SYSTEM *RESTORE - time period for recovery recommendations

When doing a STRRCYBRM *SYSTEM *RESTORE, what are the recommendations for Time period for recovery?

1) Let it default as below, *BEGIN *END?
2) Or should you reference your last system save?
3) Other options?

I found in testing that when you let it default, it includes libraries that are no longer on the system, from old saves that are not expired.

Start time and date:
Beginning time . . . . . . . . *AVAIL
Beginning date . . . . . . . . *BEGIN
End time and date:
Ending time . . . . . . . . . *AVAIL
Ending date . . . . . . . . . *END

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
http://www.pencor.com/



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.