More fun with XA STORAGE POOL 255
I changed the size of XA STORAGE POOL 255 from 5100 to I0000 in our
PROD CV and that made all the SOS I was seeing in the CV messages go
away but I still get the GETSTG messages. (note that none of the SOS
counters ever showed anything other than 0)
I went ahead and defined an XA PROGRAM POOL on our test CV to see if the
DMCL would get loaded there and it did BUT it is still in the MEM MAP at
a second address???? All of the DMCL buffers are defined as OPSYS
STORAGE. So the buffer pools should NOT reside within IDMS unless there
isn't enough OPSYS STORAGE.
queue twilight zone music....
Maybe this new extra XA STORAGE POOL that Chris is referring to exists
in Rel 15.0? I did a display mem at both B9FE000 and C3FB388 and there
is the DMCL and DM58 control block. Anyone see anything like this on
their systems?
D MEM C3FB388
<Addr> <Offset> <Hex> <Character>
0C3FB388 00000000 C4D4F5F8 8000C3E5 F0F1C4D4 C3D30166
DM58..CV01DMCL..
V1 ENTER NEXT TASK CODE:
D MEM B9FE000
<Addr> <Offset> <Hex> <Character>
0B9FE000 00000000 C4D4F5F8 8000C3E5 F0F1C4D4 C3D30166
DM58..CV01DMCL..
V1 ENTER NEXT TASK CODE:
D MEM MAP
RHDCOESA 9310 OPT 19030 CSA 1A050 LKM
1C760
CCE 460A0 SCAAREA 48280 RUA 4A380 NLT
4B420
PTT 4D000 QDT 4D860 TCA 4F5C0 DCEAREA
4F600
TCEAREA 50400 MPMODTBL 68C00 ECBLIST 692E0 CSVCAREA
69760
PGMPOOL 6C000 RENTPOOL 198000 IDMSDBIO 198058 RHDCD04W
1CE000
RHDCD0ZU 1CF600 RHDCD07Q 1D2C00 STGPOOL 34C000 HIADDR
540000
SVC250 C2C350 ESE A396810 EREAREA B068680 LTT
B787FC0
TCESTACK B791200 ABENDSTG B8362C0 TDT B836C20 PDT
B83D340
SCT B8A57A0 TRCEBUFS B8A7000 RCA B8A7020 RLEAREA
B8A70E0
RCEAREA B8B07E0 DPEAREA B8C42E0 ILEAREA B8C9620 XAPGMPL
B9FE000
XARENTPL BA7B000 IDMSDBMS BA7B058 RHDCRUSD BC1AE00 RHDCLGSD
BC1B800
RHDCDEAD BC1C200 XASTGPL C201000 CV01DMCL C3FB388
D ACTIVE XA PROGRAMS
*** Display of XA Program Pool ***
Pages in pool 125
Bytes in pool 512000
Loads to pool 1
Pages loaded 48
Load conflicts 0
CURRENT ALLOCATIONS
Pages allocated 48 38% of pool
Pages in use by one program 0 0% of pool
Pages in use by multiple programs 0 0% of pool
High-Water mark of pages allocated 48 38% of pool
Loads into unallocated space 1 100% of loads
Loads overlaying program not in use 0 0% of loads
Loads overlaying program in use 0 0% of loads
Program -----Library------ Typ Uct Siz Calls Loads
Address
CV01DMCL CDMSLIB NMN *00 191 00000001 000001
0B9FE000
Thanks and have a great weekend.
Tim
Tim Kupin
IDMS DBA
IBM Global Services
office 864.609.3564
cell 301.752.6857
home office 301.638.7424
timkupin@us.ibm.com
tim_kupin@comcast.net
=20
From: Chris Hoelscher <
choelscher@HUMANA.COM>
=20
To:
IDMS-L@LISTSERV.IUASSN.COM
=20
Date: 09/16/2009 05:24 PM
=20
Subject: Re: [IDMSVENDOR-L] XA STORAGE POOL 255
=20
Sent by: IDMS Public Discussion Forum <
IDMS-L@LISTSERV.IUASSN.COM>
=20
just a reminder ....
in release 17 - the DMCL
always gets loaded into a ""dynamc"" 2nd pool
255
- separate and apart from the ""sysgenned"" 1st pool 255 - this ""dynamic""
2nd poll 255 will always be the size of the DMCL (no bigger, no smaller)
and will appear to all commands to be 100% full (so yes, 2 pool 255s
will
show)
Chris Hoelscher
Senior IDMS & DB2 Database Administrator Humana Inc
502-476-2538
choelscher@humana.com
you only need to test the programs that you want to work correctly
From:
Tim Kupin <
timkupin@US.IBM.COM>
To:
IDMSVENDOR-L@LISTSERV.IUASSN.COM
Date:
09/16/2009 05:19 PM
Subject:
Re: [IDMSVENDOR-L] XA STORAGE POOL 255
Sent by:
IDMS 3rd-party providers forum <
IDMSVENDOR-L@LISTSERV.IUASSN.COM>
Thanks to those who responded.
We are running Release 15.0
I think Bill Allen hit the nail on the head in his off list email. We
don't have an XA PROGRAM POOL defined (I have no idea why not) which is
where it sounds like the DMCL is supposed to reside.
We do have an XA REENTRANT PROGRAM POOL.
Anyway, I bumped the size of XA STROAGE POOL 255 from 5100 to 10000. The
first 2 GETSTG's were asking for about 5100k and if the DMCL is in
there, it 's full at startup.
More will be revealed. And I'll let you guys know.
Thanks
Tim Kupin
IDMS DBA
IBM Global Services
office 864.609.3564
cell 301.752.6857
home office 301.638.7424
timkupin@us.ibm.com
tim_kupin@comcast.net
The information transmitted is intended only for the person or entity to
which it is addressed and may contain CONFIDENTIAL material. If you
receive this material/information in error, please contact the sender
and delete or destroy the material/information.
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
Normal
Normal
Re: [IDMSVENDOR-L] XA STORAGE POOL 255
"All,
Since IDMS R12 the DMCL LOAD module and the Run time DMCL have been
different. The internal structures are completely different. If you
really want to see the differences then take a look at #DMCLDS or you
could assemble it with TYPE=COMPILE for the load module control block
formats and with TYPE=DSECT for run time control block formats.
So IDMS loads the DMCL and then from it builds the run time DMCL.
The DMCL is load into XA program pool and then the run time DMCL is
build in the XA storage pool. This explains why the size seen at R17 for
the second XA storage pool 255 is not the same size as the DMCL load
module.
Not sure why it gets loaded into XA program pool as I do not believe it
is used after the runtime built.
Pete