ackup completing (and reducing the
log to zero) I then recommend to immediately remove the safety valve log
volume.
Steffan
- Original Message -
From: "William F. Colwell" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, February 28, 2002 1:13 PM
Subject: Re: logm
://www.nyherji.is
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Wholey, Joseph (TGA\MLOL)
Sent: 28. febrúar 2002 20:40
To: [EMAIL PROTECTED]
Subject: logmode/bufpoolsize/mpthreading
Environment:
Server: 4.1.3.0
Platform: S390
1. Logmode: We&#x
Hi Joe,
Our environment is same as yours - Os/390 TSM4.1.3.0.
We run roll-forward mode on the recovery log.
Size currently allocated for the recovery log = 5364Meg
The maximum you can make this is in the region of 5.4 Gig -
check back in the archives - it has been discussed before.
It depends on
Hi Joe,
At 03:39 PM 2/28/2002 -0500, you wrote:
>Environment:
>Server: 4.1.3.0
>Platform: S390
>
>1. Logmode: We're going to change the Logmode from Normal to Roll Forward. What
>determines the amount of disk I'll require?
You need enough log space to hold all the db changes between scheduled
Environment:
Server: 4.1.3.0
Platform: S390
1. Logmode: We're going to change the Logmode from Normal to Roll Forward. What
determines the amount of disk I'll require?
2. Bufpoolsize: We're going to increase from 24576K to ?. What's the determining
factor?
3. Mpthreading: We're going to
> Environment:
> Server: 4.1.3.0
> Platform: S390
>
> 1. Logmode: We're going to change the Logmode from Normal to Roll Forward. What
>determines the amount of disk I'll require?
>
> 2. Bufpoolsize: We're going to increase from 24576K to ?. What's the determining
>factor?
>
> 3. Mpthreading
