ca.portal.admin

Re:Re: Diagnostics and Symbol tables - another question

Discussion created by ca.portal.admin on Jan 31, 2008
for a load area member,:

Description: The DPROG-171 record type is used by the CA-IDMS/DC online
debugger. Each DPROG-171 occurrence represents a program load module
for which a symbol table has been established. Currently, symbol tables
can be established only for CA-ADS dialogs.


Chris Hoelscher
Senior IDMS & DB2 Database Administrator Humana Inc
502-476-2538
choelscher@humana.com



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 Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: ONE LARGE DMCL BUFFER
"One thing I would worry about is working set size and how CPU-constrained
the CV is. If memory, paging and sucking the very last cycle out of a
single processor is not a concern, then go for it.

As to why... Since IDMS uses a least-most-recently used algorithm in the
buffers, the entire buffer pool likely remains among the most popular pages
in the address space. To the extent that large buffer pages are (at times)
inefficiently used, there could be a tendency to inflate the working set
size beyond what a more constrained set of buffers would create.

If real memory is an issue, then increased paging due to this may impact the
ability of CV to deliver the overall workload. Page faults impact
(depending on MT setting) the ENTIRE region/workload, extra I/Os (due to
smaller buffer pools) impact directly only those workloads using the
overloaded buffer (and indirectly other workloads competing for storage and
program pool space... but typically not CPU).

The above is probably another fine example of overanalysis....

Don Casey
Run Right, LLC

Outcomes