Gary_Cherlet

V18 upgrade - learn from my mistakes

Discussion created by Gary_Cherlet on Jan 15, 2012
Latest reply on Jan 21, 2012 by Gary_Cherlet
One CV was configured as follows in V17 (REGION=2047M)

V21 RHDCPARM FREESTG RELEASED... 4,000K
V21 REGION NEEDED TO START UP... 8,516K
V21 TOTAL AMOUNT OF XA STORAGE.. 45,920K
V21 SYSTEM CONFIGURATION SIZE... 50,432K
V21 STORAGE RETURNED TO OPSYS... 160K

In V18 - failed as follows:

DC390001 V21 INSUFFICIENT REGION DETECTED AT STARTUP

After altering:

RHDCPARM FREESTG RELEASED... 3,000K
REGION NEEDED TO START UP... 7,640K
TOTAL AMOUNT OF XA STORAGE.. 46,176K
SYSTEM CONFIGURATION SIZE... 50,812K
STORAGE RETURNED TO OPSYS... 1,036K

No storage pools nor program pools were changed A few observations

If a freestg 3000K allowed 1036K to re returned, shouldn't have 4000K allowed 35K to re returned?? (maybe there is some threshold that must be met) The region needed to startup and total amount of XA storage both went down in V18 - yet the sys vonfig size went up!

In another CV that did not need adjusting:
V17

RHDCPARM FREESTG RELEASED... 5,000K
REGION NEEDED TO START UP... 8,300K
TOTAL AMOUNT OF XA STORAGE.. 122,948K
SYSTEM CONFIGURATION SIZE... 126,244K
STORAGE RETURNED TO OPSYS... 376K

V18
RHDCPARM FREESTG RELEASED... 5,000K
REGION NEEDED TO START UP... 8,440K
TOTAL AMOUNT OF XA STORAGE.. 123,204K
SYSTEM CONFIGURATION SIZE... 126,636K
STORAGE RETURNED TO OPSYS... 236K

So if you are close on RETURNED TO OPSYS - you may need to DECREASE FREESTG when going to V18

I have no doubt I will have more later (whether you want it or not)

Chris Hoelscher

Outcomes