× 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.



On source system, a full BRMS control group save.

STRBKUBRM CTLGRP(SAVFULL05) BMJOB(*NO) APPEND(*YES) ACTIVITY(*CTLGRPATR) RETENTION(*DAYS 45).

CTLGRP SAVFULL05 defined below.

10 *EXIT *******
20 *SAVSECDTA FFFFFFF *NO
30 *SAVCFG FFFFFFF *NO
40 *EXIT FFFFFFF
50 *ALLUSR *SYSBAS FFFFFFF *ERR *YES QSYSOPR *NONE
60 *EXIT FFFFFFF
70 *ALLDLO FFFFFFF *NO *YES
80 *EXIT FFFFFFF
90 *LINK *ALLAVL FFFFFFF *NO *NO
100 *EXIT *******

Paul

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Laurence Chiu
Sent: Wednesday, April 22, 2020 6:07 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: BRMS full copy versus Cumulative Copy between two Power systems

Hi Paul

That sounds promising. So do I have a similar command issued at the source site to create the cumulative backup? The two servers are connected via IP of course else we could not do FTP.

Thanks

On Thu, Apr 23, 2020 at 8:49 AM Steinmetz, Paul via MIDRANGE-L < midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

I do this on a normal basis, using BRMS.
By individual library.
RSTLIBBRM
No FTP.
On the target system

Cause . . . . . : Command to execute is: RSTLIBBRM SAVLIB(CABLEFILES)
DEV(TAPMLB01) SAVLVL(*CURRENT) SAVDATE(010119 *LATEST) ENDOPT(*LEAVE)
OPTION(*ALL) MBROPT(*ALL) ALWOBJDIF(*ALL) RSTASP(01) FROMSYS(PENCOR05).

Notice the FROMSYS
It is pointing back to my source production system.

FROMSYS(PENCOR05)

Paul

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Laurence Chiu
Sent: Wednesday, April 22, 2020 4:39 PM
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: BRMS full copy versus Cumulative Copy between two Power
systems

Sorry if this question seems a bit simple but in my defence I am not a
Power systems expert and my only source of expertise is our outsourcer
and I want an independent view also to validate what they tell me.

The situation is the environment I am working is has two Power
installations (IBMi of course) and each night a full backup of the
database is taken and FTP'ed to a second site and restore. The command
to create the back looks like this


https://smex-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3
a%2f%2fbit.ly%2f2yw6kdz&umid=2f943d10-036c-4d2d-bbf9-ce24e44f9cf4&auth
=438b0784514c1757bd202125ca4db8b0abdb021e-3ce3672d66ebc2413d573f15550e
80456352009f

I have blanked out sensitive information like filenames but I presume
the command still makes sense.

The output files are then sent to the other installation and restored.
At the moment the second Power server is only a few hundred metres
away and connected over GbE. So no problems. But the second server is
now being moved 2600Km away and on a 200Mbs line. That is causing
network issues. It seems to me that if the command above is a full
copy, then a better solution might be to take a cumulative
(differential I am used to saying from my DBA days) and sending that
across. That would be significantly smaller. My question is, can this
cumulative copy be loaded in the target system when records of the
last full copy don't really exist in the target BRMS. Unless once the
full copy was loaded in the target system, then a full copy was taken
to create that record. But would BRMS be smart enough to know that the
subsequent Cumulative was related to the full copy taken remotely.

Thanks
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com

As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.