I suspect the 120 second default wait time may be a big factor.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Justin Taylor
Sent: Thursday, April 25, 2019 10:08 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: RTVTCPINF times
Some nights RTVTCPINF takes a few seconds, other nights a few minutes. We're seeing that in our backup for other things as well. One night the overall process is 25 minutes, and the next 40 minutes.
-----Original Message-----
From: Steinmetz, Paul via MIDRANGE-L [mailto:midrange-l@xxxxxxxxxxxxxxxxxx]
Sent: Wednesday, April 24, 2019 9:33 PM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
Subject: RE: RTVTCPINF times
Justin,
We use BRMS, SWA, both production and r&d.
The only services we stop is HTTP *ADMIN and IBM CDC replication.
A few GUI omits, and some IFS folders set not to save.
RTVTCPINF only takes a few seconds on either lpar.
By default, any library object, if locked, (SWA can't handle all object types), will add 2 minutes.
IBM CDC replication had 30 locked objects, added 60 minutes to save, decided to end that service.
Paul
--
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@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
