RE: Strange DASD Utilization Issue

Thanks!  That's what he's trying to track down in his "spare" time.  He
thinks he probably "forgot" a close statement in one of his many programs.
Now I just have to sit tight until he figures out where it is.

Thanks for the assist.

Deb


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Gary Monnier
Sent: Tuesday, February 28, 2006 1:46 PM
To: Midrange Systems Technical Discussion
Subject: RE: Strange DASD Utilization Issue

Debbie,

Your developer needst to look at the CLOSE statement if an OPEN is used
and the COMMIT statement if database tables are updated.  They will need
to determine where in their code these statements need to be placed.

Gary Monnier | Senior Software Developer

19426 68th Ave. S
Kent, WA 98032
(253) 872-7788
gary.monnier@xxxxxxxxxxxxx
www.powertech.com 


-----Original Message-----
From: midrange-l-bounces+gary.monnier=powertech.com@xxxxxxxxxxxx
[mailto:midrange-l-bounces+gary.monnier=powertech.com@xxxxxxxxxxxx] On
Behalf Of DebbieKelemen
Sent: Tuesday, February 28, 2006 12:25 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Strange DASD Utilization Issue


Tom,

You nailed it on the head!  I went & looked at his code & he has no clue
as
to how to delete these things.  I'm not sure how to tell him to fix
this.
He says he is always closing his connection.  But he is going to try to
research it.  He wants me to give him more specifics about it.

Debbie


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Gary Monnier
Sent: Tuesday, February 28, 2006 11:33 AM
To: Midrange Systems Technical Discussion
Subject: RE: Strange DASD Utilization Issue

Debbie,

How often do your network jobs utilizing ODBC/JDBC close their database
connections?  I've seen several customers have unusual ASP usage due to
client programs creating new cursors each time they access the iSeries
database.  The previously opened cursors leave open data paths and over
time they add up.

Look at the number of open files (DSPJOB, option 14) for several of your
QZDASOINIT jobs.  If you see what to you seems to be a large list of
open files and some start repeating it is usually a pretty safe bet that
a client has some cursor creation and deletion issues.


Another ODBC/JDBC issue that can occur is when a client program does not
perform a commit often enough.  The uncommitted transactions still have
to be tracked and that takes up space and memory.  An example would be
where you have 1000 clients performing database updates and the client
only performs a commit when it ends.  If this only occurs once a day
then all those transactions stay in the server's cache.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of DebbieKelemen
Sent: Tuesday, February 28, 2006 9:44 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Strange DASD Utilization Issue


Tom,

I guess my next step would be since we are 24x7 with the web would be to
figure out which subsystems I can end & bring back up without impacting
the
web jobs.  And my guess is - it's the web jobs that are my biggest
offenders
in this whole thing.  I just need a way to prove it to my IT Director on
paper so I can justify shutting things down for a few minutes.  Which is
what it really takes.

Deb


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
qsrvbas@xxxxxxxxxxxx
Sent: Monday, February 27, 2006 6:50 PM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Strange DASD Utilization Issue

midrange-l-request@xxxxxxxxxxxx wrote:

>   3. Strange DASD Utilization Issue (DebbieKelemen)
>
>After an IPL, my system is at a nice 38.64% utilization.  Within a day
it
>has grown to 42.98%.  I can guarantee within a few weeks I will be up
to 50
>or more percent and I will need to IPL to get my DASD down for the mid
60%
>within a 6 week period or so.
>
>When I run a GO DISKTASK, it shows that Temporary space is 5% of my
system.
>That is what my system grew by.  How do I keep my temporary space under
>control?  

Debbie:

I not clear on why 5% temp storage would seem to be unusual. Without
knowing
how "big" your system is and how it's used, there's no way to really
guess;
but 5% is a reasonable amount.

With nothing else to go on, I'd say you're in great shape.

One minor note... A good part of "temporary storage" can be reclaimed
without an IPL. Simply ending and restarting your various subsystems
will
handle a lot of it. That directly implies that the jobs in those
subsystems
are also ended. As days go by, system server jobs, subsystem monitors,
etc.,
have joblogs and other elements take little bits of storage temporarily.
When the jobs are ended, some of the stuff in temporary storage gets
moved
into permanent storage, e.g., spooled joblogs, and other stuff is simply
deleted.

Tom Liotta