We're using IBM's admin tool 5.1 with maintenance thru 12/04. We are still running z/os V7 on the mainframe. We've been experience a lot of errors that IBM says is related to insufficient region size. I've been told that the latest version of the admin tool can take up to 12 meg of memory to run. We've been told to check the Le parms and other parameters but nothing too specific. For example, I pull up a trigger in the admin tool and type DDL next to it, I get this type of error.
'ERROR' condition was raised
Traceback of user routines:
Compile Unit Entry Statement CU offset Entry offset Address
ADB2PA ADB2PA 725 +000005C4 +000005BC 14A6146C
ADB2REG PARSE_SQL_STMT 4798 +0003DF86 +0000021E 14C7BCE6
ADB2REG EDIT_TRIGGER 4640 +0003B76E +00000216 14C794CE
ADB2REG CREATE_TRIGGER 3224 +000279F6 +00000B62 14C65756
ADB2REG ADB2REG 766 +0000052E +00000526 14C3E28E
ADB2GEN GENERATE 17825 +0005E7C0 +0000080C 14C14010
ADB2GEN GEN_TRIGGER 9221 +0002BD12 +00000F06 14BE1562
ADB2GEN ADB2GEN 501 +000018F6 +000018EE 14BB7146
CEE0813S Insufficient storage was available to satisfy a get storage
(CEECZST)
request.
From compile unit ADB2PA at entry point ADB2PA at statement 725 at com
pile unit offset +000005C4 at entry
offset +000005BC at address 14A6146C.
User abend 4,038 dec occurred processing command 'DSN '.

I've also got calls on the "MIG" command blowing up in the TSO forground. I don't know if this is a z/os thing, Admin tool thing, or if it's a DB2 v7 thing. We're having memory problems with large applications just "abending" with memory problems on the z/os side. To me, it's all to coincidental. Anyone else out there with these problems? Any comments/help would be appreciated.

(No, I haven't used the Admin Tool since V1 - when it was a toy.)

Have you tried using a larger (any?) SIZE on your logon panel?

James Campbell

yes, we're logging on with 20 meg. we have some configuration on the z/os side (not my area) that is not allowing us the 20 meg we ask for, or there some sort of memory leak with db2 out there.

Part of your TSO profile is the maximum region size you can request. Depending on your system configuration it might be in SYS1.UADS, your RACF profile TSO segment, or elsewhere. You'll have to discuss this with your sys progs.

James Campbell